Transmission management apparatus, transmission management system, transmission management method, and transmission management program

ABSTRACT

A transmission system determines whether property data of a transmission terminal matches property data of a counterpart terminal to generate similarity information indicating the degree of similarity between the property data of the transmission terminal and the property data of the counterpart terminal, and determines a destination to which the event data specifying an event created by the transmission terminal is to be transmitted based on the similarity information.

CROSS-REFERENCE TO RELATED APPLICATIONS

This patent application is a continuation of U.S. application Ser. No. 13/040,750, filed Mar. 4, 2011, and is based on and claims priority under 35 U.S.C. §119 to Japanese Patent Application Nos. 2010-049136, filed on Mar. 5, 2010, and 2011-007900, filed on Jan. 18, 2011, in the Japanese Patent Office, the entire disclosure of each of which are incorporated herein by reference.

FIELD OF THE INVENTION

The present invention generally relates to an apparatus, system, and method of managing a terminal that transmits or receives image data and/or voice data to or from another terminal through a network.

BACKGROUND

With the need for reducing costs or times associated with business trips, more companies are moving towards transmission systems to have teleconference or videoconference among remotely located offices via a communication network. The transmission systems allow transmission of image data or voice data among a plurality of transmission terminals that are remotely located from one another through a communication network such as the Internet to facilitate communication among the plurality of transmission terminals.

The recent transmission systems may be provided with a function of sending notification to one or more transmission terminals that are previously determined when the state of the request transmission terminal changes, for example, as described in Japanese Patent Application Publication No. 2006-295883.

SUMMARY

In the system described in Japanese Patent Application Publication No. 2006-295883, there may be a transmission terminal that does not receive notification even when the transmission terminal requires such notification, as a transmission terminal that should receive notification tends to change under various conditions.

In view of the above, example embodiments of the present invention include an apparatus, method, system, computer program and product each capable of determining whether property data of a transmission terminal matches property data of a counterpart terminal to generate similarity information indicating the degree of similarity between the property data of the transmission terminal and the property data of the counterpart terminal, and determining a destination to which the event data specifying an event created by the transmission terminal is to be transmitted based on the similarity information.

In addition to the above-described example embodiments, the present invention may be practiced in various other ways. For example, the destination to which the event data is to be transmitted may be determined based on other factors in addition to the similarity information.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete appreciation of the disclosure and many of the attendant advantages and features thereof can be readily obtained and understood from the following detailed description with reference to the accompanying drawings, wherein:

FIG. 1 is a schematic block diagram illustrating a transmission system according to an example embodiment of the present invention;

FIG. 2 is an illustration for explaining transmission or reception of data such as image data, voice data, or management data, performed by the transmission system of FIG. 1;

FIGS. 3A to 3C are illustrations for explaining image quality of image data transmitted or received by the transmission system of FIG. 1;

FIG. 4 is a perspective view illustrating the outer appearance of a terminal of the transmission system of FIG. 1, according to an example embodiment of the present invention;

FIG. 5 is a schematic block diagram illustrating a hardware structure of the terminal of the transmission system of FIG. 1;

FIG. 6 is a schematic block diagram illustrating a hardware structure of any one of a transmission management system, a relay terminal, a program providing system, and maintenance system of FIG. 1;

FIG. 7 is a schematic block diagram illustrating functional structures of the transmission management system, the terminal, and the relay terminal, of the transmission system of FIG. 1;

FIG. 8 is a schematic block diagram illustrating a functional structure of a secondary relay terminal selection unit of the terminal of FIG. 7;

FIG. 9 is a schematic block diagram illustrating a primary relay terminal selection unit of the transmission management system of FIG. 7;

FIG. 10 is an example data structure of a data quality management table, managed by the relay terminal of FIG. 7;

FIG. 11 is an example data structure of a relay terminal management table, managed by the transmission management system of FIG. 7;

FIG. 12 is an example data structure of a terminal authentication management table, managed by the transmission management system of FIG. 7;

FIG. 13 is an example data structure of a terminal management table, managed by the transmission management system of FIG. 7;

FIG. 14 is an example data structure of a candidate list management table, managed by the transmission management system of FIG. 7;

FIG. 15 is an example data structure of a session management table, managed by the transmission management system of FIG. 7;

FIG. 16 is an example data structure of an address priority management table, managed by the transmission management system of FIG. 7;

FIG. 17 is an example data structure of a transmission speed priority management table, managed by the transmission management system of FIG. 7;

FIG. 18 is an example data structure of a quality management table, managed by the transmission management system of FIG. 7;

FIG. 19 is a data sequence diagram illustrating operation of managing state information indicating an operation state of the relay terminal of the transmission system of FIG. 1, according to an example embodiment of the present invention;

FIG. 20 is a data sequence diagram illustrating operation of establishing communication among two or more transmission terminals of the transmission system of FIG. 1, according to an example embodiment of the present invention;

FIG. 21 is a data sequence diagram illustrating operation of limiting a number of candidate relay terminals, performed by the transmission system of FIG. 1;

FIG. 22 is a flowchart illustrating operation of limiting a number of candidate relay terminals, performed by the transmission management system of FIG. 1;

FIG. 23 is a table storing priority points of the relay terminals that are respectively calculated by the transmission management system of FIG. 1 during the operation of limiting a number of candidate relay terminals;

FIGS. 24A and 24B are a data sequence diagram illustrating operation of selecting a relay terminal, performed by the transmission system of FIG. 1;

FIG. 25 is a flowchart illustrating operation of selecting a relay terminal, performed by the transmission terminal of FIG. 1;

FIG. 26 is a data sequence diagram illustrating operation of transmitting or receiving data such as image data and voice data, performed by two or more transmission terminals of the transmission system of FIG. 1;

FIG. 27 is an example property data management table, managed by the transmission management system of FIG. 1;

FIG. 28 is an example event data management table, managed by the transmission management system of FIG. 1;

FIG. 29 is an example destination management table, managed by the transmission management system of FIG. 1;

FIG. 30 is a schematic block diagram illustrating a functional structure of an event data transmit of the transmission management system of FIG. 1;

FIG. 31 is a schematic block diagram illustrating a functional structure of an event log management system of the transmission management system of FIG. 1;

FIG. 32 is an example event log management table, managed by the event log management system of the transmission system of FIG. 1;

FIG. 33 is a data sequence diagram illustrating transmitting event data from one terminal to another terminal or to the event log management system, performed by the transmission system of FIG. 1, according to an example embodiment of the present invention;

FIG. 34 is a flowchart illustrating operation of transmitting event data, performed by the transmission management system of FIG. 1.

The accompanying drawings are intended to depict example embodiments of the present invention and should not be interpreted to limit the scope thereof. The accompanying drawings are not to be considered as drawn to scale unless explicitly noted.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the present invention. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “includes” and/or “including”, when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

In describing example embodiments shown in the drawings, specific terminology is employed for the sake of clarity. However, the present disclosure is not intended to be limited to the specific terminology so selected and it is to be understood that each specific element includes all technical equivalents that operate in a similar manner.

<Configuration of Transmission System>

FIG. 1 is a schematic block diagram illustrating a configuration of a transmission system 1 according to an example embodiment of the present invention. FIG. 2 is an illustration for explaining transmission or reception of various data such as image data, voice data, and management data, performed by the transmission system 1 of FIG. 1. FIGS. 3A to 3C are illustrations for explaining quality of image data transmitted by the transmission system 1 of FIG. 1.

Referring to FIG. 1, the transmission system 1 mainly includes a transmission management system 50, and a plurality of transmission terminals 10 aa, 10 ab, 10 ac, 10 ba, 10 bb, 10 bc, 10 ca, 10 cb, 10 cc, 10 da, 10 db, and 10 dc. Any one of the terminals 10 transmits or receives contents data such as image data and/or voice data to or from any other one of the terminals 10.

In one example, the transmission system 1 functions as a data providing system that transmits contents data from one transmission terminal to another transmission terminal in one direction through the transmission management system 50. In another example, the transmission system 1 functions as a two-way communication system that exchanges various information including image data and/or voice data that is used to convey human's feelings between or among two or more of the plurality of transmission terminals 10 each of which functioning as a communication terminal, through the transmission management system 50 that functions as a communication management system. When functioning as the communication system, the transmission system 1 may be implemented as a videoconference system or video teleconference system.

In the following examples, it is assumed that the transmission system 1 of FIG. 1 is implemented as the videoconference system, which is one example structure of the communication system. Based on this assumption, the transmission management system 50 is implemented as the videoconference communication management system, which is one example structure of the communication management system. Further, the transmission terminal 10 is implemented as the videoconference communication terminal, which is one example structure of the communication terminal. However, the use of transmission system 1 is not limited to the following examples such that the transmission system 1 may be implemented as the transmission system or the communication system as described above. Examples of the transmission system 1 include, but not limited to, videoconference system, teleconference system, voice conference system, voice teleconference system, and image data sharing system that shares an image being displayed onto a screen.

Referring to FIG. 1, the transmission system 1 further includes a plurality of displays 120 aa, 120 ab, 120 ac, 120 ba, 120 bb, 120 bc, 120 ca, 120 cb, 120 cc, 120 da, 120 db, and 120 dc, a plurality of relay terminals 30 a, 30 b, 30 c, and 30 d, an event log management system 80, a program providing system 90, and a maintenance system 100, which are connected through a communication network 2 including the Internet 2 i. FIG. 1 also shows a plurality of routers 70 a, 70 b, 70 c, 70 d, 70 ab, and 70 cd.

For the descriptive purposes, in this example, the transmission management system 50 may be referred to as the “management system” 50. Any number of the plurality of terminals 10 aa to 10 dc may be collectively or each referred to as the terminal 10. Any number of the plurality of displays 120 aa to 120 dc may be collectively or each referred to as the display 120. Any one of the plurality of relay terminals 30 a, 30 b, 30 c, and 30 d may be collectively or each referred to as the relay terminal 30. The terminal 10 that transmits data to another terminal 10 to carry out videoconference is referred to as the request terminal 10A. The terminal 10 that receives data from another terminal 10 to carry out videoconference is referred to as the counterpart terminal 10B. For example, the request terminal 10A includes any terminal 10 that requests another terminal 10 to start videoconference, and the counterpart terminal 10B includes any terminal 10 that is requested by the request terminal 10A to start videoconference.

As illustrated in FIG. 2, in the transmission system 1, the request terminal 10A and the counterpart terminal 10B first establish a management data session sei to start transmission and reception of various types of management data through the management system 50. Further, in this example, the request terminal 10A and the counterpart terminal 10B establish four contents data sessions sed to transmit or receive contents data through the relay terminal 30. The four contents data sessions, which may be referred to as image and/or voice data sessions, include a session “HL” to transmit high-level resolution image data HL, a session “ML” to transmit medium-level resolution image data ML, a session “LL” to transmit low-level resolution image data LL, and a session “V” to transmit voice data V.

Referring now to FIGS. 3A to 3C, various image data having different resolution levels, which are respectively transmitted by the terminal 10 of the transmission system 1, are explained. Referring to FIG. 3A, the low-level resolution image data, which functions as a base image, has 160 pixels in the horizontal direction and 120 pixels in the vertical direction. Referring to FIG. 3B, the medium-level resolution image data has 320 pixels in the horizontal direction and 240 pixels in the vertical direction. Referring to FIG. 3C, the high-level resolution image data has 640 pixels in the horizontal direction and 480 pixels in the vertical direction. In case of communicating with a narrowband signal line, low-quality image data that is generated based on the low-level resolution image data, which is the base image, is transmitted. In case of communicating with a wideband signal line, medium-quality image data that is generated based on the low-level resolution image data and the medium-level resolution image data is transmitted. In case of communicating with a broadband signal line, high-quality image data that is generated based on the low-level resolution image data, the medium-level resolution image data, and the high-level resolution image data is transmitted. Any one of the above-described types of image data may be transmitted together with voice data.

The relay terminal 30 of FIG. 1 relays contents data that is transmitted between the plurality of terminals 10. The management system 50 controls operation of the transmission system 1, for example, by performing authentication of a user at the terminal 10 through the login process, management of operation state of the terminal 10, management of a candidate list, management of operation state of the relay terminal 30, etc. In this example, the image data may be any desired data such as a moving picture and/or a still image.

The plurality of routers 70 a to 70 cd, which may be collectively or each referred to as the router 70, selects a route that is most suitable for transmitting contents data such as image data and voice data.

The event log management system 80, which includes a hard disk device (HD) 204 (FIG. 6), stores log data in association with a specific function or operation performed by the transmission terminal 10.

The program providing system 90 includes a hard disk device (HD) 204 (FIG. 6), which stores a terminal control program that causes the terminal 10 to perform various functions or operations. For example, the program providing system 90 sends the terminal control program to the terminal 10 through the Internet 2 i to cause the terminal 10 to install the terminal control program. Further, the HD 204 of the program providing system 90 may store a relay control program that causes the relay terminal 30 to perform various functions or operations. For example, the program providing system 90 sends the relay control program to the relay terminal 30 through the Internet 2 i to cause the relay terminal 30 to install the relay control program. Further, the HD 204 of the program providing system 90 may store a transmission management program that causes the management system 50 to perform various functions or operations. For example, the program providing system 90 sends the transmission management program to the management system 50 to cause the management system 50 to install the transmission management program. Further, the HD 204 of the program providing system 90 may store an event log management program that causes the event log management system 80 to perform various functions or operations. For example, the program providing system 90 sends the event log management program to the event log management system 80 to cause the event log management system 80 to install the event log management program.

The maintenance system 100 is implemented as a computer capable of maintaining, managing, fixing, or upgrading at least one of the terminal 10, relay terminal 30, management system 50, event log management system 80, and program providing system 90. Assuming that the maintenance system 100 is provided within a country, and the terminal 10, the relay terminal 30, the management system 50, the event log management system 80, and the program providing system 90 are each installed outside the country, the maintenance system 100 maintains, manages, fixes, or upgrades at least one of the terminal 10, relay terminal 30, management system 50, event log management system 80, and program providing system 90, remotely through the communication network 2. The maintenance system 100 may manage maintenance of at least one of the terminal 10, relay terminal 30, management system 50, event log management system 80, and program providing system 90 without using the communication network 2. For example, a machine type number, a manufacturing number, customer information, maintenance and repair information, and failure log information may be maintained at the maintenance system 100 without using the communication network 2.

Still referring to FIG. 1, the terminals 10 aa, 10 ab, and 10 ac, the relay terminal 30 a, and the router 70 a are connected to a local area network (LAN) 2 a. The terminals 10 ba, 10 bb, and 10 bc, the relay terminal 30 b, and the router 70 b are connected to a LAN 2 b. The LAN 2 a and the LAN 2 b are connected to a leased line 2 ab in which the router 70 ab is provided. It is assumed that these devices including the terminals 10 aa to 10 bc are located in an area A. For example, assuming that the area A is any area in Japan, the LAN 2 a could be located within an office in a city such as Tokyo, and the LAN 2 b could be located within an office in another city such as Osaka.

The terminals 10 ca, 10 cb, and 10 cc, the relay terminal 30 c, and the router 70 c are connected to a LAN 2 c. The terminals 10 da, 10 db, and 10 dc, the relay terminal 30 d, and the router 70 d are connected to a LAN 2 d. The LAN 2 c and the LAN 2 d are connected to a leased line 2 cd in which the router 70 cd is provided. It is assumed that these devices including the terminals 10 ca to 10 dc are located in an area B apart from the area A. For example, assuming that the area is any area in the United States, the LAN 2 c could be located within an office in a city such as New York, and the LAN 2 d could be located within an office in another city such as Washington, D.C. The area A and the area B are connected through the Internet 2 i, via the routers 70 ab and 70 cd.

The management system 50, the event log management system 80, and the program providing system 90 are connected through the Internet 2 i to the terminal 10 and the relay terminal 30. Any one of the management system 50, the event log management system 80, and the program providing system 90 may be located at any location within or outside any one of the area A and the area B.

In this example, the communication network 2 includes the LAN 2 a, LAN 2 b, leased line 2 ab, Internet 2 i, leased line 2 cd, LAN 2 c, and LAN 2 d. Any one or any portion of these lines or any other lines that may be included in the communication network 2 may be implemented as wired network or wireless network such as Wireless Fidelity (WiFi) network or Bluetooth network.

As shown in FIG. 1, the terminal 10, the relay terminal 30, the management system 50, the router 70, the event log management system 80, and the program providing system 90 are each provided with four digit numbers. These four digit numbers separated by dots are the simple expressions of IP addresses respectively assigned to any one of the devices shown in FIG. 1, each of which has a function of communication device. For example, the IP address of the terminal 10 aa is “1.2.1.3”. For simplicity, it is assumed that the IP address is expressed in IPv4. Alternatively, the IP address may be expressed in IPv6.

Further, in this example, the terminal 10 may be communicated in various ways. For example, at least two different terminals 10 that are located at different rooms in the same office, or at least two different terminals 10 that are located at different offices that are remotely located from one another, may communicate with one another. In another example, at least two different terminals 10 that are located in the same room may communicate with one another. In another example, one terminal 10 that is located indoor and another terminal 10 that is located outdoor, or at least two different terminals 10 that are both located outdoor, may communicate with one another. When the terminal 10 is located outdoor, the terminal 10 communicates with the other terminal 10 through a wireless network such as a wireless network designed for a mobile phone.

<Hardware Structure of Transmission System>

Next, a hardware structure of the transmission system 1 is explained according to an example embodiment of the present invention. In this example, when any delay in data reception is observed at the counterpart terminal 10B or the relay terminal 30, the relay terminal 30 changes resolution of image data to obtain converted image data and sends the converted image data to the counterpart terminal 10B or the request terminal 10A.

FIG. 4 is a perspective view illustrating the outer appearance of the terminal 10 of the transmission system 1. As illustrated in FIG. 4, the terminal 10 includes a body 1021, an arm 1074, and a camera housing 1075. The body 1021 includes a front side wall 1021 a having a plurality of air intake holes 1021 e that are formed over the nearly entire surface of the front side wall 1021 a. The body 1021 further includes a back side wall 1021 b having a plurality of exhaust holes over the nearly entire surface of the back side wall 1021 b. When a cooling fan that is provided within the body 1021 is driven, air flows in through the intake holes 1021 e of the front side wall 1021 a and out through the exhaust holes of the back side wall 1021 b. The front side wall 1021 a is further provided with a sound pickup hole 1021 f, which is formed at a central portion of the front side wall 1021 a. Through the sound pickup hole 1021 f, a microphone 114 (FIG. 5) of the terminal 10 is able to catch sounds such as human voice or any sound including noise.

The body 1021 has an operation panel 1022, which is provided at the left portion when viewed from the top. The operation panel 1022 includes a plurality of operation buttons 108 (“the operation button 108”), a power switch 109, and a plurality of sound output holes 1022 f. Through the sound output holes 1022 f, a speaker 115 (FIG. 5) of the terminal 10 is able to output sounds such as sounds generated based on human voice. The body 1021 further includes a holder 1021 p, which is provided at the right portion when viewed from the top. The holder 1021 p, which has a concave shape, accommodates therein the arm 1074 and the camera housing 1075.

The arm 1074 is fixed to the body 1021 via a torque hinge 1073. With the torque hinge 1073, the arm 1074 can be rotated in all directions of up, down, right, and left, with respect to the top surface of the body 1021, while making a pan angle θ1 that ranges from −180 degrees to +180 degrees and a tilt angle θ2 that ranges from 0 to 90 degrees with the top surface of the body 1021. When the arm 1074 is tilted at a relative tilt angle of 45 degrees, a click sound is generated.

The camera housing 1075 incorporates therein a camera 112 that takes an image of an object. The object may be a part of a user or a room where the terminal 10 is located. The camera housing 1075 is fixed to the arm 1074 through a torque hinge 1075 a. With the torque hinge 1075 a, the camera housing 1075 can be rotated with respect to the arm 1074, while making a tilt angle θ3 that ranges from about +100 degrees to −90 degrees in the direction toward the front side wall 1021 a of the body 1021. The camera housing 1075 makes a tilt angle of 0 degree with respect to the arm 1074 when the camera housing 1075 and the arm 1074 are on the same plane.

Further, as illustrated in FIG. 4, the terminal 10 is connected to the display 120 through a cable 120 c.

The relay terminal 30, management system 50, event log management system 80, and program providing system 90 are each implemented by a general-purpose computer such as a personal computer or a server computer. For simplicity, explanation of the outer appearance of the computer is omitted.

FIG. 5 illustrates a hardware structure of the terminal 10 according to an example embodiment of the present invention. The terminal 10 includes a central processing unit (CPU) 101, a read only memory (ROM) 102, a random access memory (RAM) 103, a flash memory 104, a solid state drive (SSD) 105, a medium drive 107, the operation button 108, the power switch 109, a network interface (I/F) 111, the camera 112, an imaging element interface (I/F) 113, the microphone 114, the speaker 115, a voice input/output interface (I/O I/F) 116, a display interface (I/F) 117, and an outside device connection interface (I/F) 118, which are electrically connected through a bus 110 such as an address bus or data bus.

The CPU 101 controls entire operation of the terminal 10. The ROM 102 stores therein a control program for execution by the CPU 101, such as an initial program loader (IPL). The RAM 103 functions as a work area of the CPU 101. The flash memory 104 stores therein various data such as the terminal control program, image data, or voice data. The SSD 105 controls reading or writing of various data with respect to the flash memory 104 under control of the CPU 101. The medium drive 107 controls reading or writing of various data with respect to a removable recording medium 106 such as a flash memory. The operation button 108 allows the user to input a user instruction, for example, by allowing the user to select a communication destination such as the counterpart terminal 10B. The power switch 109 allows the user to switch on or off the power of the terminal 10. The network I/F 111 allows the terminal 10 to transmit data through the communication network 2.

The camera 112 takes an image of an object to obtain image data under control of the CPU 101. The imaging element I/F 113 controls operation of the camera 112. The microphone 114 catches sounds such as voice. The speaker 115 outputs sounds such as sounds generated based on voice. The voice I/O I/F 116 controls input or output of sound signals such as voice signals with respect to the microphone 114 and the speaker 115 under control of the CPU 101. The display I/F 117 transmits image data to the display 120 under control of the CPU 101. The outside device connection I/F 118 controls connection of the terminal 10 to various types of outside device.

The display 120 may be implemented by a liquid crystal display (LCD) or an organic light emitting display, which displays various data such as an image of an object or an operation icon. As illustrated in FIGS. 4 and 5, the display 120 is connected to the display I/F 117 through the cable 120 c. The cable 120 c may be implemented by an analog RCB (VGA) signal cable, a component video cable, a high-definition multimedia interface (HDMI) signal cable, or a digital video interactive (DVI) signal cable.

The camera 112 includes a plurality of devices such as a lens system, and a solid-state image sensing device that photo-electrically converts a light to generate an image of an object. For example, the solid-state image sensing device includes a complementary metal oxide semiconductor (CMOS) or a charge coupled device (CCD).

The outside device connection I/F 118 may be connected to an outside device such as a camera, microphone, or speaker through a universal serial bus (USB) cable. When the outside camera is connected to the terminal 10, the CPU 101 causes the terminal 10 to capture an image using the outside camera, rather than the camera 112 that is incorporated in the terminal 10. When the outside microphone or the outside speaker is connected to the terminal 10, the CPU 101 causes the terminal 10 to use the outside microphone or the outside speaker in replace of the incorporated microphone 114 or the incorporated speaker 115.

The recording medium 106, which can be freely attached to or detached from the terminal 10, includes any desired type of recording medium. In alternative to the flash memory 104, any nonvolatile memory that is readable and writable under control of the CUP 101 may be used such as Electrically Erasable and Programmable ROM (EEPROM).

The terminal control program may be written onto a recording medium that is readable by a general-purpose computer such as the recording medium 106 in any format that is installable or executable by a general-purpose computer. Once the terminal control program is written onto the recording medium, the recording medium may be distributed. Further, the terminal control program may be stored in any desired memory other than the flash memory 104, such as the ROM 102.

FIG. 6 illustrates a hardware structure of the management system 50 of FIG. 1. The management system 50 includes a CPU 201, a ROM 202, a RAM 203, the HD 204, a hard disk drive (HDD) 205, a medium drive 207, a display 208, a network interface (I/F) 209, a keyboard 211, a mouse 212, and a CD-ROM drive 214, which are electrically connected through a bus 210 such as an address bus or a data bus.

The CPU 201 controls entire operation of the management system 50. The ROM 202 stores a control program for execution by the CPU 201, such as the IPL. The RAM 203 functions as a work area of the CPU 201. The HD 204 stores therein various data such as a transmission management program. The HDD 205 controls reading or writing of various data with respect to the HD 204 under control of the CPU 201. The medium drive 207 controls reading or writing of various data with respect to a removable recording medium 206 such as a flash memory. The display 208 displays various data such as a cursor, menu, window, character, or image. The network I/F 209 allows the management system 50 to transmit data through the communication network 2. The keyboard 211 includes a plurality of keys, each of which is used for inputting a user instruction through a character, a numeral, or a symbol. The mouse 212 allows the user to input a user instruction including, for example, selection or execution of a specific instruction, selection of an area to be processed, and instruction of cursor movement. The CD-ROM drive 214 controls reading or writing of various data with respect to a CD-ROM 213. In alternative to the CD-ROM 213, any removable recording medium may be used.

The transmission management program may be written onto a recording medium that is readable by a general-purpose computer such as the recording medium 206 or the CD-ROM 213 in any format that is installable or executable by the general-purpose computer. Once the transmission management program is written onto the recording medium, the recording medium may be distributed. Further, the transmission management program may be stored in any desired memory other than the HD 204, such as the ROM 202.

The relay terminal 30 is substantially similar in hardware structure to the management system 50 of FIG. 6, except for replacement of the transmission management program with a relay terminal control program that is used for controlling the relay terminal 30. The relay terminal control program may be written onto a recording medium that is readable by a general-purpose computer such as the recording medium 206 or the CD-ROM 213 in any format that is installable or executable by the general-purpose computer. Once the relay terminal control program is written onto the recording medium, the recording medium may be distributed. Further, the relay terminal control program may be stored in any desired memory other than the HD 204, such as the ROM 202.

The event log management system 80 is substantially similar in hardware structure to the management system 50 of FIG. 6, except for replacement of the transmission management program with an event log management program that is used for controlling the event log management system 80. The event log management program may be written onto a recording medium that is readable by a general-purpose computer such as the recording medium 206 or the CD-ROM 213 in any format that is installable or executable by the general-purpose computer. Once the event log management program is written onto the recording medium, the recording medium may be distributed. Further, the event log management program may be stored in any desired memory other than the HD 204, such as the ROM 202.

The program providing system 90 is substantially similar in hardware structure to the management system 50 of FIG. 6, except for replacement of the transmission management program with a program providing program that is used for controlling the program providing system 90. The program providing program may be written onto a recording medium that is readable by a general-purpose computer such as the recording medium 206 or the CD-ROM 213 in any format that is installable or executable by the general-purpose computer. Once the program providing program is written onto the recording medium, the recording medium may be distributed. Further, the program providing program may be stored in any desired memory other than the HD 204, such as the ROM 202.

The maintenance system 100 is substantially similar in hardware structure to the management system 50 of FIG. 6.

Other examples of removable recording medium, which may be used in replace of the CD-ROM 213, include, but not limited to, compact disc recordable (CD-R), digital versatile disk (DVD), and blue ray disc.

<Functional Structure of Transmission System>

Referring now to FIG. 7, a functional structure of the transmission system 1 of FIG. 1 is explained according to an example embodiment of the present invention. More specifically, FIG. 7 illustrates a functional structure of the management system 50, a functional structure of the terminal 10, and a functional structure of the relay terminal 30. As illustrated in FIG. 1, the terminal 10, the relay terminal 30, and the management system 50 exchange data with one another through the communication network 2. For simplicity, the program providing system 90 and the event log management system 80 of FIG. 1 is not shown in FIG. 7.

<Functional Structure of Terminal>

The terminal 10 includes a data transmit/receive 11, an operation input 12, a login request 13, an imaging unit 14, a voice input 15 a, a voice output 15 b, a secondary relay terminal selection unit 16, a display control 17, a delay detector 18, and a memory control 19. These units that are shown in FIG. 7 correspond to a plurality of functions or functional modules, which are executed according to an instruction of the CPU 101 (FIG. 5) that is generated according to the terminal control program being loaded from the flash memory 104 onto the RAM 103.

The terminal 10 further includes a memory 1000 that may be implemented by, for example, the RAM 103 (FIG. 5) and the flash memory 104 (FIG. 5).

Referring now to FIGS. 5 and 7, a functional structure of the terminal 10 is explained according to an example embodiment of the present invention. More specifically, in this example, the operations or functions that are performed by the terminal 10, which include the operations or functions performed by the units shown in FIG. 7, are performed in relation to one or more hardware devices of the terminal 10 that are shown in FIG. 5.

The operations or functions of the data transmit/receive 11 of the terminal 10 of FIG. 7 are performed by the network I/F 111 of FIG. 5 according to an instruction received from the CPU 101. The data transmit/receive 11 transmits or receives various data or information to or from another terminal, device, or system, through the communication network 2. In this example, the data transmit/receive 11 starts receiving state information that indicates the state of each candidate counterpart terminal 10 from the management system 50, before starting communication with any counterpart terminal 10B. With the state information of the candidate terminal 10, the user at the request terminal 10A is able to know the operation state of the candidate terminal 10. The operation state of the candidate terminal 10 indicates whether the candidate terminal 10 is on-line or off-line, whether the user at the candidate terminal 10 is having a session, or whether the user at the candidate terminal 10 is available or not available. The state information of the candidate terminal 10 further indicates various other types of information regarding the candidate terminal 10, such as whether the cable 120 c is disconnected from the candidate terminal 10, whether the candidate terminal 10 is capable of outputting voice data but not to capable of outputting image data, or whether the candidate terminal 10 operates in MUTE mode in which no sounds are output. For the descriptive purposes, in the following examples, it is assumed that the state information of the candidate terminal 10 at least indicates the operation state of the candidate terminal 10.

The operations or functions of the operation input 12 of the terminal 10 of FIG. 7 are performed by the operation button 108 and the power switch 109 (FIG. 5) according to an instruction received from the CPU 101. The operation input 12 receives a user instruction input by the user through the operation button 108 or the power switch 109. For example, when the user selects “ON” using the power switch 109, the operation input 12 receives a user instruction for turning the power on, and causes the terminal 10 to turn on the power.

The operations or functions of the login request 13 are performed according to an instruction received from the CPU 101. When the power of the terminal 10 is turned on, the login request 13 automatically causes the data transmit/receive 11 to send login request information that requests the login process, and a current IP address of the terminal 10, to the management system 50 through the communication network 2. When the power of the terminal 10 is turned off according to a user instruction received from the user through the power switch 109, the login request 13 causes the data transmit/receive 11 to send current state information of the terminal 10 to the management system 50, which indicates that the power of the terminal 10 is turned off After the state information is sent, the operation input 12 turns off the power of the terminal 10. As the state information of the terminal 10 is sent every time the power is turned off, the management system 50 is able to know that the terminal 10 is off-line in realtime.

The operations or functions of the imaging unit 14 of the terminal 10 of FIG. 7 are performed by the camera 112 and the imaging element IN 113 according to an instruction received from the CPU 101. The imaging unit 14 takes an image of an object to output image data of the object.

The operations or functions of the voice input 15 a of the terminal 10 of FIG. 7 are performed by the voice input/output I/F 116 according to an instruction received from the CPU 101. After the microphone 114 converts voice of the user at the terminal 10 to a voice signal, the voice input 15 a inputs the voice signal in the form of voice data.

The operations or functions of the voice output 15 b of the terminal 10 of FIG. 7 are performed by the voice input/output I/F 116 according to an instruction received from the CPU 101. The voice output 15 b outputs a voice signal of voice data that is received from another terminal 10 through the speaker 115.

The secondary relay terminal selection unit 16 selects one of the relay terminals 30 that is suitable for communication to start videoconference. More specifically, according to an instruction received from the CPU 101 (FIG. 5), the secondary relay terminal selection unit 16 performs selection of the relay terminal 30 using a counter 16 a, a calculator 16 b, and a secondary selector 16 c as illustrated in FIG. 8.

The counter 16 a obtains date and time information indicating the date and time at which the data transmit/receive 11 of the terminal 10 receives preparatory transmit information when the preparatory transmit information is transmitted from another terminal 10. The calculator 16 b calculates a time period T between the time when the preparatory information is transmitted by another terminal 10 and the time when the preparatory information is received at the terminal 10, based on the difference between the time and date information obtained by the counter 16 a and time and date information included in the preparatory transmit information.

The secondary selector 16 c selects one of the relay terminals 30 having the minimum value of the time period T calculated by the calculator 16 b.

The operations or functions of the display control 17 of the terminal 10 of FIG. 7 are performed by the display I/F 117 according to an instruction received from the CPU 101. The display control 17 controls transmit of image data to the display 120. The image data is generated by combining image data of different resolutions. Further, the display control 17 transmits candidate list information received from the transmission management system 50 to the display 120 to cause the display 120 to display a candidate list based on the candidate list information.

The delay detector 18 detects a delay time ms indicating a time period in which contents data such as image data or voice data sent through the relay terminal 30 from another terminal 10 is delayed, according to an instruction received from the CPU 101 (FIG. 5).

The memory control 19 is implemented by the SSD 105 (FIG. 5) according to an instruction received from the CPU 101. The memory control 19 stores various data in the memory 1000, or read out various data from the memory 1000. The memory 1000 stores therein various data such as terminal identification (ID) information for identifying the terminal 10, a password for authenticating the terminal 10 or a user at the terminal 10, a secret key assigned to the terminal 10, and a public key assigned to the authentication system 80. The memory control 19 further overwrites a memory space in the memory 1000 to store image data and/or voice data every time the terminal 10 communicates with another terminal 10. Before overwriting image data with new image data, the memory control 19 reads out the image data for display on the display 120, and the voice data for output through the speaker 150.

In this example, any one of the terminal ID of the terminal 10 and the relay terminal ID of the relay terminal 30 includes any type of identification information that can be expressed by any language, character, symbol, mark, or any combination of language, character, symbol, and mark.

<Functional Structure of Relay Terminal>

Referring to FIG. 7, the relay terminal 30 includes a data transmit/receive 31, a state detector 32, a data quality checker 33, a data quality manager 34, a data quality changer 35, and a memory control 39. Upon execution, the CPU 201 (FIG. 6) loads the relay terminal control program from the HD 204 onto the RAM 203 to cause one or more of the units illustrated in FIG. 6 to perform functions or operations shown in FIG. 7. The relay terminal 30 further includes a memory 3000 that may be implemented by the RAM 203 and/or the HD 204 (FIG. 6).

The memory 3000 includes a data quality management database (DB) 3001, which stores a data quality management table illustrated in FIG. 10. The data quality management table of FIG. 10 stores an Internet protocol (IP) address of the counterpart terminal 10B to which image data is transmitted through the relay terminal 30, in association with quality of image data to be transmitted through the relay terminal 30 to the counterpart terminal 10B.

(Functional Structure of Relay Terminal)

Next, a functional structure of the relay terminal 30 is explained according to an example embodiment of the present invention. More specifically, in this example, the operations or functions that are performed by the relay terminal 30, which include the operations or functions performed by the units shown in FIG. 7, are performed in relation to one or more hardware devices of the relay terminal 10 that are shown in FIG. 6.

The data transmit/receive 31 of FIG. 7 is implemented by the network I/F 209 of FIG. 6 according to an instruction received from the CPU 201. The data transmit/receive 31 transmits or receives various data to or from another terminal, device, or system through the communication network 2.

The state detector 32, which is implemented by the CPU 201 of FIG. 6, detects an operation state of the relay terminal 30. The operation state includes the on-line state (“ON LINE”), the off-line state (“OFF LINE”), the communicating state, and the holding state. The on-line state is a state in which the relay terminal 30 is turned on and available for data transmission/reception. The off-line state is a state in which the relay terminal 30 is not available for data transmission/reception, for example, as the power is not turned on. The communicating state is a state in which the relay terminal 30 is on-line, but is communicating with another terminal. The holding state is a state in which the relay terminal 30 is on-line, but is not available at least for temporarily.

The data quality checker 33, which is implemented by the CPU 201 of FIG. 6, searches the data quality management DB 3001 (FIG. 11) using the IP address of the counterpart terminal 10B as a search key to extract information regarding the quality of image data suitable to communication with the counterpart terminal 10B. Based on the extracted information regarding the quality of image data, the relay terminal 30 determines the quality of image data to be transmitted to the counterpart terminal 10B.

The data quality manager 34, which may be implemented by the CPU 201 of FIG. 6, changes the contents of the data quality management DB 3001 based on the quality information that is received from the management system 50. For example, assuming that the request terminal 10 aa having the terminal ID “01aa” communicates with the counterpart terminal 10 db having the terminal ID “01db” to transmit or receive high quality image data during videoconference, transmission of image data may delay for various reasons. For example, if a request terminal 10 bb and a counterpart terminal 10 ca start videoconference over the communication network 2, transmission of image data from the request terminal 10 aa to the counterpart terminal 10 db tends to slow down due to the increase in traffic. In such case, the relay terminal 30 changes the quality of image data to be transmitted from high image quality to lower image quality. More specifically, the contents in the data quality management DB 3001 is changed from high-level image quality to medium-level image quality, based on the quality information indicating the use of medium-level image quality.

The data quality changer 35, which may be implemented by the CPU 201 of FIG. 6, changes the quality of image data received from the request terminal 10 to the quality of image data according to the contents of the data quality management DB 3001.

The memory control 39 is implemented by the HDD 205 according to an instruction received from the CPU 201. The memory control 39 stores various data in the memory 3000, or reads out various data from the memory 3000.

<Functional Structure of Management System>

The management system 50 includes a data transmit/receive 51, a terminal authenticator 52, a state manager 53, a terminal extractor 54, a terminal state obtainer 55, a primary relay terminal selection unit 56, a session manager 57, a quality determiner 58, a memory control 59, a delay time manager 60, and an event data transmit 61. Upon execution, the CPU 201 (FIG. 6) loads the transmission management program from the HD 204 onto the RAM 203 to cause the units shown in FIG. 6 to perform operations or functions as illustrated in FIG. 7. The management system 50 further includes a memory 5000, which may be implemented by the HD 204 of FIG. 6.

The memory 5000 includes a relay terminal management database (DB) 5001, which stores therein a relay terminal management table of FIG. 11. The relay terminal management table of FIG. 11 stores, for each relay terminal ID of the terminal 30, the operation state of the relay terminal 30, the received date and time at which the management system 50 receives the state information indicating the operation state of the relay terminal 30 from the relay terminal 30, the IP address of the relay terminal 30, and the maximum data transmission speed of the relay terminal 30 in Mbps. For example, for the relay terminal 30 a having the relay terminal ID “111a”, the relay terminal management table indicates that the operation state is “ON LINE”, the received date and time at which the management system 50 receives the state information is “13:00 PM of Nov. 10, 2009”, the IP address of the relay terminal 30 a is “1.2.1.2”, and the maximum data transmission speed of the relay terminal 30 a is 100 Mbps.

The memory 5000 further includes a terminal authentication management database (DB) 5002, which stores a terminal authentication management table of FIG. 12. The terminal authentication management table of FIG. 12 stores a plurality of terminal IDs respectively assigned to the terminals 10 that are managed by the management system 50, in association with a plurality of passwords that are previously determined for the respective terminals 10. For example, referring to the terminal authentication management table of FIG. 12, the terminal 10 aa having the terminal ID “01aa” is assigned with the password “aaaa”.

The memory 5000 further includes a terminal management database (DB) 5003, which stores a terminal management table of FIG. 13. The terminal management table of FIG. 13 stores, for each one of the terminal IDs assigned to the terminals 10, the terminal name to be used for communication with the terminal 10, the operation state of the terminal 10, the received date and time at which the management system 50 receives the login request information from the terminal 10, and the IP address of the terminal 10. For example, for the terminal 10 aa having the terminal ID “01aa”, the terminal management table of FIG. 13 indicates that the terminal name is “Japan Tokyo Office AA terminal”, the operation state is on-line (“ON LINE”) and is available for communication (“OK”), the received date and time is “13:40 PM, Nov. 10, 2009”, and the IP address of the terminal 10 aa is “1.2.1.3”.

The memory 5000 further includes a candidate list management database (DB) 5004, which stores a candidate list management table of FIG. 14. The candidate list management table of FIG. 14 stores, for each one of a plurality of request terminals 10A capable of requesting for videoconference communication, the terminal ID of the request terminal 10A, and one or more terminal IDs that are respectively assigned to candidate terminals 10 that are previously registered for the request terminal 10A. In this example, for the request terminal 10A, one or more terminals 10 of the transmission system 1 of FIG. 1 are previously registered as the candidate terminal 10. For example, the candidate list management table of FIG. 14 indicates that the request terminal 10 aa having the terminal ID “01aa” is most likely to request for videoconference with respect to the terminal 10 ab having the terminal ID “01ab”, the terminal 10 ba having the terminal ID “01ba”, the terminal 10 bb having the terminal ID “01bb”, etc. The management system 50 manages the candidate list management table of FIG. 14, for example, according to a user instruction received from any one of the terminals 10. For example, in response to a user instruction received from the terminal 10 aa, the management system 50 may add or delete the contents of the candidate list management table.

The memory 5000 further includes a session management database (DB) 5005, which stores a session management table of FIG. 15. The session management table of FIG. 15 stores information regarding each of the sessions that are carried out by at least two terminals 10 of the transmission system 1 for the purpose of selecting the relay terminal 30 that is most suitable for communication between at least two terminals 10. More specifically, for each session ID that uniquely identifies each session, the session management table of FIG. 15 stores a relay terminal ID of the relay terminal 30 to be used for transmitting or receiving contents data such as image data and voice data, a terminal ID of the request terminal 10A, a terminal ID of the counterpart terminal 10B, a delay time ms indicating a time period required for receiving contents data at the counterpart terminal 10B, the date and time information indicating the time at which the management system 50 receives delay information from the counterpart terminal 10B. For example, referring to the session management table of FIG. 15, for the session having the session ID “sel”, the relay terminal 30 a having the relay terminal ID “111a” is selected to relay contents data between the request terminal 10 aa having the terminal ID “01aa” and the counterpart terminal 10 db having the terminal ID “01db”. Further, the management system 50 receives the delay information from the counterpart terminal 10 db at 14:00 PM, Nov. 10, 2009. Based on this date and time information, the delay time ms of 200 milliseconds (ms) is obtained. In case of having videoconference between only two terminals 10, the delay time may be determined based on the time when the management system 50 receives the delay information transmitted from the request terminal 10A rather than based on the time when the management system 50 receives the delay information transmitted from the counterpart terminal 10B. In case of having videoconference with more than two terminals 10, the delay information transmitted from the counterpart terminal 10B that receives the contents data is used to manage the date and time at which the delay information is received.

The memory 5000 further includes a priority management database (DB) 5006, which stores an address priority management table of FIG. 16. The address priority management table of FIG. 16 defines a number of address priority points to be assigned to an arbitrary set of terminal 10 and relay terminal 30 based on the degree of similarity between the IP address of the terminal 10 and the IP address of the relay terminal 30. Assuming that the IP address of the terminal 10 and the IP address of the relay terminal 30 are each expressed in the form of four digital numbers as described above referring to FIG. 1, as the degree of similarity between the terminal IP address and the relay terminal IP address increases, a larger number of address priority points is assigned. In FIG. 16, the “S” indicates that one digit of the IP address, which may be referred to as the dot address, is the same for both of the terminal 10 and the relay terminal 30. The “D” indicates that one digit of the IP address, or the dot address, is different between the terminal 10 and the relay terminal 30. More specifically, in this example, when the first to third digits or dot addresses are the same between the terminal 10 and the relay terminal 30, the address priority point is 5. When the first and second digits or dot addresses are the same between the terminal 10 and the relay terminal 30, the address priority point is 3. In such case, the fourth digit or dot address does not affect the address priority point. When the first digit or dot address is the same between the terminal 10 and the relay terminal 30, the address priority point is 1. In such case, the third and fourth digits or dot addresses do not affect the address priority point. When the first digit or dot address is different between the terminal 10 and the relay terminal 30, the address priority point is 0. In such case, the second to fourth digits or dot addresses do not affect the address priority point.

The priority management DB 5006 of the memory 5000 further includes a transmission speed priority management table of FIG. 17. The transmission speed priority management table of FIG. 17 stores a range of the maximum data transmission speeds in association with a transmission speed priority point. More specifically, the transmission speed priority management table of FIG. 17 indicates that the transmission speed priority point increases with the increase in value of the maximum data transmission speeds at the relay terminal 30. For example, referring to FIG. 17, when the maximum data transmission speed at the relay terminal 30 is equal to or greater than 1000 Mbps, the transmission speed priority point of 5 is assigned. For example, when the maximum data transmission speed at the relay terminal 30 is equal to or greater than 100 Mbps but less than 1000 Mbps, the transmission speed priority point of 3 is assigned. When the maximum data transmission speed at the relay terminal 30 is equal to or greater than 10 Mbps but less than 100 Mbps, the transmission speed priority point of 1 is assigned. When the maximum data transmission speed at the relay terminal 30 is less than 10 Mbps, the transmission speed priority point of 0 is assigned.

The memory 5000 further includes a quality management database (DB) 5007, which stores a quality management table of FIG. 18. The quality management table of FIG. 18 stores the delay time ms of image data in association with the quality of image data. More specifically, the quality management table of FIG. 18 indicates that the quality of image data to be processed by the relay terminal 30 is lowered, as the delay time of the image data at the request terminal 10A or the counterpart terminal 10B increases. For example, when the delay time ms is equal to or greater than 0 milliseconds (ms), but less than 100 ms, the image data quality is high. When the delay time ms is equal to or greater than 100 ms but less than 300 ms, the image data quality is medium. When the delay time ms is equal to or greater than 300 but less than 500 ms, the image data quality is low. When the delay time ms is equal to or greater than 500 ms, the management system 50 interrupts operation of transmitting data.

The memory 5000 further stores a property data management database (DB) 5008, which stores a property data management table of FIG. 27. The property data management table of FIG. 27 stores various property data for each one of the terminals 10 that are registered to the transmission system 1 of FIG. 1. In this example, the property data management table of FIG. 27 stores a company name of the company that owns the terminal 10 and a country where the company is located, with respect to the terminal ID of the terminal 10. Other examples of property data include, but not limited to, a region where the company that owns the terminal 10 is located, a division or group within the company that owns the terminal 10, and a capability or function of the terminal 10. Alternatively or additionally, the property data may be related to information regarding a user of the terminal 10. For example, property data may indicate a company to which the user belongs, or a position of the user within the company. Referring to FIG. 27, the property data of the terminal 10 aa having the terminal ID “01aa” specifies that the terminal 10 aa is owned by the company named “A” that is located in Japan.

The memory 5000 further stores an event data management database (DB) 5009, which stores an event data management table of FIG. 28. The event data management table of FIG. 28 stores information indicating the importance level of the event identification data of a specific event of the terminal 10. The event of the terminal 10 is any process or operation that has been performed or being performed, or any operation state of the terminal 10 representing the process or operation of the terminal 10. Examples of process or operation include, but not limited to, the process of starting, interrupting, or ending the output of image data, the process of starting, interrupting, or ending the output of voice data, and the process of starting, interrupting, or ending setting operation. Examples of operation state include, but not limited to, volume of microphone 114 or speaker 115 of the terminal 10, resolution of the camera 112 of the terminal 10, information indicating whether the microphone 114 or speaker 115 is in the mute state, information indicating the connection state of microphone 114, speaker 115, or camera 112, and information indicating whether the microphone 114, the speaker 115 of the camera 112 is in the error state.

In this example, the event identification data including event main class, event sub-class, and event name specifies the operation and the state of a specific event. More specifically, the event main class specifies whether a specific event is the operation or the state. The event sub-class specifies a type of data to be processed or a type of device performing the event. The event name describes the operation or state of the event. Referring to FIG. 28, the event having the event main class of “OPERATION”, the event sub-class of “PICTURE” and the event name of “START” is assigned with the importance level of “HIGH”. This indicates that the event that starts the operation of processing picture data has the high importance level.

The memory 5000 further stores a destination management database (DB) 5010, which stores a destination management table of FIG. 29. The destination management table of FIG. 29 specifies a destination to which notification is to be transmitted when a specific event occurs at the terminal 10, in association with the similarity of the property data of the terminal 10 creating the event with respect to the counterpart terminal 10 and the importance level of the event. For example, referring to FIG. 29, notification regarding the event of the terminal 10 is sent to one or more terminals 10 having the same company name with the terminal 10 creating the event under a condition in which the terminal 10 creating the event has the same company name with the counterpart terminal 10, the company that owns the terminal 10 creating the even is located in the same country where the company that owns the counterpart terminal 10 is located, and the event generated by the terminal 10 has the high importance level.

Next, a functional structure of the management system 50 is explained according to an example embodiment of the present invention. In this example, the operations or functions that are performed by the management system 50, which include the operations or functions performed by the units shown in FIG. 7, are performed in relation to one or more hardware devices of the management system 50 that are shown in FIG. 6.

The data transmit/receive 51, which may be implemented by the network I/F 209 (FIG. 6) according to an instruction received from the CPU 201, transmits or receives various data or information to or from another terminal, device, or system through the communication network 2.

Under control of the CPU 201 (FIG. 6), the terminal authenticator 52 obtains a terminal ID and a password from the login request information that is received from the data transmit/receive 51. Using the terminal ID and the password as a search key, the terminal authenticator 52 searches the terminal authentication management DB 5002 to determine whether the obtained set of terminal ID and password is registered. Based on the search result, the terminal authenticator 52 determines whether the user at the terminal 10 or the terminal 10 is allowed for access.

The state manager 53, which operates according to an instruction received from the CPU 201 (FIG. 6), manages the operation state of the request terminal 10A that sends the login request information using the terminal management DB 5003 (FIG. 13). More specifically, the state manager 503 stores the terminal ID of the request terminal 10A, the operation state of the request terminal 10A, the date and time at which the management system 50 receives the login request information from the request terminal 10A, and the IP address of the request terminal 10A. When the power of the terminal 10 is switched from the ON state to the OFF state according to a user instruction received through the power switch 109, the state manager 53 receives the state information of the terminal 10 indicating that the terminal 10 is turned off, from the terminal 10. Based on the state information of the terminal 10, the state manager 53 changes the state information of the terminal 10 that is stored in the terminal management DB 5003 from the on-line state to the off-line state.

The terminal extractor 54, which operates according to an instruction received from the CPU 201 (FIG. 6), searches the candidate list management DB 5004 (FIG. 14) using the terminal ID of the request terminal 10A as a key to obtain a list of terminal IDs each being assigned to a plurality of candidate terminals 10. Additionally, the terminal extractor 54 searches the candidate list management DB 5004 (FIG. 14) using the terminal ID of the request terminal 10A as a key to obtain a terminal ID of another request terminal 10A that registers the request terminal 10A as a candidate terminal for another request terminal 10A.

The terminal state obtainer 55, which operates under control of the CPU 201 (FIG. 6), searches the terminal management DB 5003 (FIG. 13) using the terminal ID of each candidate terminal 10 that is extracted by the terminal extractor 54 as a key to obtain the state information of each candidate terminal 10. Accordingly, the terminal state obtainer 55 obtains the operation state of each of the candidate terminal 10 that is previously determined for the request terminal 10A that sends the login request information. Further, the terminal state obtainer 55 searches the terminal management DB 5003 using the terminal ID extracted by the terminal extractor 54 as a key to obtain the state information of the request terminal 10A that sends the login request information.

The primary relay terminal selection unit 56, which operates according to an instruction received from the CPU 201 (FIG. 6), limits a number of relay terminals 30 each of which is a candidate relay terminal 30 that may be used for relaying contents data between at least two terminals 10. Based on the result obtained by the primary relay terminal selection unit 56, the secondary relay terminal selection unit 17 of the terminal 10 selects one terminal 30 that is most suitable for communication between at least two terminals 10. As illustrated in FIG. 9, the primary relay terminal selection unit 56 includes a session ID generator 56 a, a terminal IP address extractor 56 b, a primary selector 56 c, and a priority determiner 56 d.

The session ID generator 56 a of the primary relay terminal selection unit 56 generates a session ID for identifying a session that is used for selecting the relay terminal 30. The terminal IP address extractor 56 b extracts the terminal ID of the request terminal 10A and the terminal ID of the counterpart terminal 10B respectively from the session request information received from the request terminal 10A, and searches the terminal management DB 5003 (FIG. 13) to obtain the IP address of the request terminal 10A and the IP address of the counterpart terminal 10B. The primary selector 56 c selects one or more relay terminals 30 having the online state from the relay terminal management DB 5001 (FIG. 11) to obtain the relay terminal ID of the selected relay terminal 30. In this example, it is assumed that more than two relay terminals 30 are selected as having the on-line state.

Further, the primary selector 56 c obtains the IP address of each of the selected relay terminals 30. Once the IP address of the relay terminal 30 is obtained for each relay terminal 30, the primary selector 56 c compares the IP address of the relay terminal 30 with at least one of the IP address of the request terminal 10A and the IP address of the counterpart terminal 10B that are respectively obtained by the terminal IP address extractor 56 b to analyze the degree of similarity between the IP address of the terminal 10 and the IP address of the relay terminal 30. More specifically, the primary selector 56 c compares between the IP address of the terminal 10 and the IP address of the relay terminal 30, digit by digit, or dot address by dot address, to determine the degree of similarity. Using the address priority management table of FIG. 16, the primary selector 56 c obtains the address priority point for each one of the relay terminals 30. Assuming that the primary selector 56 c compares the IP address of the terminal 10 with the IP address of the relay terminal 30, respectively for the request terminal 10A and the counterpart terminal 10B, the primary selector 56 c obtains two address priority points for each one of the relay terminals 30. In such case, the primary selector 56 c selects the highest one of the address priority points as the address priority point for the relay terminal 30.

Additionally, for each of the selected relay terminals 30 having the on-line state, the primary selector 56 c obtains the maximum data transmission speed of the relay terminal 30 from the relay terminal management table of FIG. 11. Using the transmission speed priority management table of FIG. 17, the primary selector 56 c obtains the transmission speed priority point that corresponds to the maximum data transmission speed of the selected relay terminal 30, for each of the selected relay terminals 30.

For each of the relay terminals 30, the primary selector 56 c obtains a total priority point by adding the address priority point and the transmission speed priority point together. In this example, the primary selector 56 c selects two relay terminals 30 including the relay terminal 30 having the highest total priority point and the relay terminal 30 having the second highest total priority point.

In this example, a number of relay terminals 30 that is finally selected by the primary selector 56 c is not limited to two such that more than two relay terminals 30 may be finally selected for further processing as long as a number of relay terminals 30 is sufficiently reduced.

The priority determiner 56 d refers to the priority management DB 5006 (FIG. 16) to determine the address priority point for each one of the relay terminals 30 that is selected by the primary selector 56 c. The priority determiner 56 d obtains the maximum data transmission speed of the relay terminal 30 from the relay terminal management DB 5001 (FIG. 11), and refers to the priority management DB 5006 (FIG. 17) to obtain the transmission speed priority point of the relay terminal 30 that is selected by the primary selector 56 c.

Referring back to FIG. 7, the session manager 57, which operates according to an instruction received from the CPU 201, stores the session ID generated by the session ID generator 56 a, the terminal ID of the request terminal 10A, and the terminal ID of the counterpart terminal 10B, in a corresponding manner, in the session management DB 5005 (FIG. 15) of the memory 5000. The session manager 57 further stores the relay terminal ID of the relay terminal 30 that is finally selected by the secondary selector 17 c of the terminal 10 for each session ID, in the session management DB 5005 (FIG. 15).

The quality determiner 58, which operates according to an instruction received from the CPU 201 (FIG. 6), searches the quality management DB 5007 (FIG. 18) using the delay time ms obtained for the selected relay terminal 30 to obtain the image data quality that is desirable for communication using the relay terminal 30.

The memory control 59, which operates according to an instruction received from the CPU 201 (FIG. 6) in relation with the HDD 205 (FIG. 6), stores various data in the memory 5000 or reads out various data from the memory 5000.

The delay time manager 60 searches the terminal management DB 5003 (FIG. 13) using the IP address of the counterpart terminal 10B to obtain the terminal ID of the counterpart terminal 10B. The delay time manager 60 further manages the session management table of FIG. 15 stored in the session management DB 5005 so as to keep updated the value stored in the “delay time” field for the obtained terminal ID of the counterpart terminal 10B.

The event data transmit 61 transmits notification to another terminal 10 or the event log management system 80 when an event occurs at the terminal 10. In this example, event data is sent as the notification to specify the operation or the operation state of the event occurred at the terminal 10. As illustrated in FIG. 30, the event data transmit 61 includes an importance level obtainer 61 a, a property data obtainer 61 b, a determiner 61 c, and a destination extractor 61 d. The event data includes event identification data including data specifying the event main class, the event class, and the event name of a specific event, and the terminal ID of the terminal 10 that created the event.

The importance level obtainer 61 a obtains the importance level of a specific event. In operation, the importance level obtainer 61 a refers to the event data management table of FIG. 28 stored in the event data management DB 5009 to obtain the importance level for the specific event that is stored in association with the event data identification data of the specific event.

The property data obtainer 61 b obtains property data of the terminal 10 that created the event, and property data of the counterpart terminal 10 that communicates with the terminal 10 creating the event. The property data obtainer 61 b includes a first property data obtainer 61 b 1, a communicating terminal data obtainer 61 b 2, and a second property data obtainer 61 b 3.

The first property data obtainer 61 b 1 searches the property data management table of FIG. 27 stored in the property data management DB 5008 using the terminal ID of the terminal 10 that created the event as a search key to obtain the property data regarding the terminal ID of the terminal 10 creating the event.

The communicating terminal data obtainer 61 b 2 searches the session management table of FIG. 15 stored in the session management DB 5005 using the terminal ID of the terminal 10 creating the event to obtain the terminal ID of the counterpart terminal 10 as the terminal ID of the communicating terminal 10.

The second property data obtainer 61 b 3 searches the property data management table of FIG. 27 stored in the property data management DB 5008 using the terminal ID of the communicating terminal 10 as a search key to obtain the property data of the communicating terminal 10.

The determiner 61 c determines whether the property data of the terminal 10 that is obtained by the first property data obtainer 61 b 1 is the same as the property data of the communicating terminal 10 that is obtained by the second property data obtainer 61 b 3 to generate a determination result indicating the similarity of property data between the terminal 10 creating the event and the communicating terminal 10.

The destination extractor 61 d searches the destination management table of FIG. 29 stored in the destination management DB 5010 using a combination of the similarity of property data that is obtained by the determiner 61 c and the importance level of the event data that is obtained by the importance level obtainer 61 a, to obtain a destination to which the event data is to be transmitted.

<Functional Structure of Event Log Management System>

Referring now to FIG. 31, a functional structure of the event log management system 80 is explained according to an example embodiment of the present invention. The event log management system 80 includes a data transmit/receive 81 and a memory control 89. In this example, the operations or functions that are performed by the event log management system 80, which include the operations or functions performed by the units shown in FIG. 31, are performed in relation to one or more hardware devices of the event log management system 80 that are shown in FIG. 6. More specifically, in this example, the ROM 202 stores therein an event log management program. Upon execution by the CPU 201, the event log management program is loaded from the ROM 202 onto the RAM 203 to cause the event log management system 80 to perform operations or functions according to the event log management program.

The event log management system 80 further includes a memory 8000, which may be implemented by the HD 204 of FIG. 6.

The memory 8000 stores an event log management DB 8001, which stores an event log management table of FIG. 32. The event log management table of FIG. 32 stores, for each event identification (ID) for uniquely identifying a specific event, the date and time at which the event occurred, the event identification data including the event main class, the event sub-class, and the event name, and the terminal ID of the terminal 10 that created the event. For example, referring to FIG. 32, information regarding the event having the event ID “00001” indicates that the event occurred at 11:40, Jan. 27, 2010, and the event has the main event class of “OPERATION”, the event sub-class of “PICTURE”, and the event name of “START”, and that the terminal 10 that created the event has the terminal ID “01aa”.

Referring now to FIG. 6 and FIG. 31, a functional structure of the event log management system 80 is explained according to an example embodiment of the present invention.

The data/transmit 81, which is implemented by the network I/F 209 (FIG. 6) according to an instruction received from the CPU 201, transmits or receives various data or information to or from another terminal, device, or system through the communication network 2.

The memory control 89, which operates according to an instruction received from the CPU 201 (FIG. 6) in relation with the HDD 205 (FIG. 6), stores various data in the memory 8000 or reads out various data from the memory 8000.

<Operation of Transmission System>

Referring now to FIGS. 19 to 34, operation performed by the transmission system 1 is explained according to an example embodiment of the present invention. FIG. 19 is a data sequence diagram illustrating operation of managing state information indicating the operation state of the relay terminal 30, which is sent from the relay terminal 30 to the management system 50, according to an example embodiment of the present invention. FIGS. 20A and 20B are a data sequence diagram illustrating operation of preparing for communication to be established between or among two or more of terminals 10. FIG. 21 is a data sequence diagram illustrating operation of selecting the relay terminal 30. FIG. 22 is a flowchart illustrating operation of selecting the relay terminal 30. FIG. 23 is a table for explaining operation of calculating a total priority point to be used for operation of selecting the relay terminal 30. FIGS. 24A and 24B are a data sequence diagram illustrating operation of selecting the relay terminal 30. FIG. 25 is a flowchart illustrating operation of selecting the relay terminal 30, performed by the terminal 10. FIG. 26 is a data sequence diagram illustrating operation of transmitting or receiving contents data such as image data and/or voice data to or from one terminal to another terminal. FIG. 33 is a data sequence diagram illustrating operation of transmitting event data of the terminal 10 to another terminal 10 or the event log management system 80, performed by the transmission system 1 of FIG. 1. FIG. 34 is a flowchart illustrating operation of transmitting event data, performed by the management system 50.

Referring now to FIG. 19, operation of managing state information of the terminal 30, which is sent from each terminal 30 to the management system 50, performed by the transmission system 1 is explained according to an example embodiment of the present invention. In this example, it is assumed that the relay terminals 30 a, 30 b, 30 c, and 30 d, which may be each or collectively referred to as the relay terminal 30, exit in the transmission system 1.

At S1-1, S1-2, S1-3, and S1-4, the relay terminals 30 a, 30 b, 30 c, and 30 d each periodically monitors the operation state of the relay terminal 30. This monitoring is performed by the state detector 32 (FIG. 7) of the relay terminal 30.

At S2-1, S2-2, S2-3, and S2-4, the data transmit/receive 31 of the relay terminal 30 periodically transmits state information of the relay terminal 30 to the management system 50 through the communication network 2. With the state information of the relay terminal 30 that is periodically received, the management system 50 is able to manage the operation state of the relay terminal 30 in realtime. The state information of the relay terminal 30 includes an operation state of the relay terminal 30 that is detected by the state detector 32 of the relay terminal 30, which is sent together with a relay terminal ID that uniquely identifies each relay terminal 30. For the descriptive purposes, in this example, it is assumed that the relay terminals 30 a, 30 b, and 30 d each have the on-line state, and the relay terminal 30 c has the off-line state due to the failure in relay control program of the relay terminal 30 c.

At S3-1, S3-2, S3-3, and S3-4, the management system 50 receives the state information from the relay terminal 30 at the data transmit/receive 51, and stores the received state information of the relay terminal 30 in the memory 5000 through the memory control 59. More specifically, the memory control 59 stores the state information of each relay terminal 30 in association with the relay terminal ID of the corresponding relay terminal 30 in the relay terminal management DB 5001 (FIG. 11).

For example, referring to FIG. 11, the management system 50 stores the state information of the relay terminal 30 indicating whether the relay terminal 30 is on-line, off-line, or in trouble, etc., in association with the relay terminal ID of the relay terminal 30. Additionally, the management system 50 stores the date and time information indicating the time when the management system 50 receives the state information of the relay terminal 30 in association with the relay terminal ID of the relay terminal 30. When the management system 50 does not receive any state information from the relay terminal 30, the relay terminal management table of FIG. 11 has an empty value for the “operation state” field and the “date and time” field for the subjected relay terminal 30. Alternatively, the value of the “operation state” field and the value of the “date and time” field may reflect the state information that is previously sent by the subjected relay terminal 30 to the management system 50 it the relay terminal management table of FIG. 11 retains such value.

Referring to FIGS. 20A and 20B, operation of transmitting and receiving various management data before starting videoconference between the request terminal 10 aa and the counterpart terminal 10 db is explained, according to an example embodiment of the present invention. More specifically, the operation of FIGS. 20A and 20B is performed during a management data session sei in which various management data is exchanged.

At S20, the user at the request terminal 10 aa turns on the power of the request terminal 10 aa through the power switch 109 (FIG. 5). The operation input 12 of the request terminal 10 aa (FIG. 7) turns on the power of the request terminal 10 aa.

At S22, as the power is turned on, the login request 13 of the request terminal 10 aa automatically causes the data transmit/receive 11 to send the login request information that requests the login process to the management system 50 through the communication network 2. The login request information includes the terminal ID of the request terminal 10 aa and the password. More specifically, the memory control 19 reads out the terminal ID and the password from the memory 1000, and sends the read data to the data transmit/receive 11. The data transmit/receive 11 of the request terminal 10 aa sends the login request information including the terminal ID and the password to the management system 50. At the time of sending the login request information from the request terminal 10 aa to the management system 50, the request terminal 10 aa sends an IP address of the request terminal 10 aa such that the management system 50 knows the IP address of the request terminal 10 aa.

At S23, the terminal authenticator 52 of the management system 50 searches the terminal authentication management DB 5002 (FIG. 12) stored in the memory 5000 using the terminal ID and the password of the login request information received through the data transmit/receive 51. When it is determined that the terminal ID and the password of the login request information is stored in the terminal authentication management DB 5002, the terminal authenticator 52 determines that the terminal 10 aa is a registered terminal that is authorized to use the transmission system 1.

At S24, when the terminal authenticator 52 determines that the login request information is received from the authorized terminal 10, the state manager 53 of the management system 50 stores the operation state, the date and time at which the login request information is received, and the IP address of the terminal 10 aa, with respect to the terminal ID and the terminal name of the terminal 10 aa in the terminal management DB 5003 (FIG. 13) to create a record of the terminal 10 aa. Using the terminal management table of FIG. 13, which stores the operations state of online, the date and time of “13:40, 11/10/2009”, and the terminal IP address of “1.2.1.3” in association with the terminal ID “01aa”, various information regarding the terminal 10 aa can be managed.

Referring to FIG. 20, at S25, the data transmit/receive 51 of the management system 50 sends the authorization result obtained by the terminal authenticator 52 to the request terminal 10 aa that has sent the login request information through the communication network 2. As described above, in this example, it is assumed that the terminal authenticator 52 determines that the terminal 10 aa is an authorized terminal.

When the request terminal 10 aa receives the authorization result indicating that the terminal 10 aa is authorized, the data transmit/receive 11 sends the candidate list request information that requests for a candidate list to the management system 50 through the communication network 2. The data transmit/receive 51 of the management system 50 receives the candidate list request information.

At S26, the terminal extractor 54 of the management system 50 searches the candidate list management DB 5004 (FIG. 14) using the terminal ID “01aa” of the request terminal 10 aa that has sent the login request information to extract a terminal ID for each of candidate terminals 10 that are previously registered for the request terminal 10 aa. More specifically, referring to FIG. 14, the terminal extractor 54 extracts terminal IDs including “01ab”, “01ba”, “01db”, etc. of terminals 10 ab, 10 ba, 10 db, etc. to obtain information regarding candidate terminals for the request terminal 10 aa.

At S27, the terminal state obtainer 55 searches the terminal management table stored in the terminal management DB 5003 (FIG. 13) using the candidate terminal ID of the candidate terminal that is extracted by the terminal extractor 54 as a search key to obtain the operation state of the candidate terminal having the extracted candidate terminal ID. More specifically, in this example, referring to FIG. 13, the terminal state obtainer 55 obtains the operation states “off-line”, “on-line”, and “on-line” respectively for the terminal IDs “10ab”, “10ba”, and “10db”.

At S28, the data transmit/receive 51 of the management system 50 sends the candidate state information including the terminal ID and the operation state of the candidate terminal obtained at S26 and S27, to the request terminal 10 aa through the communication network 2. More specifically, in this example, the terminal IDs “01ab”, “01ba”, and “01db” and the operation states “off-line”, “on-line” and “on-line” that are obtained respectively for the candidate terminals 10 ab, 10 ba, and 10 db are sent. With this candidate state information, the request terminal 10 aa is able to know the current operation state of each of the candidate terminals 10.

At S29, the terminal extractor 54 of the management system 50 searches the candidate list management table stored in the candidate list management DB 5004 (FIG. 14) using the terminal ID “01aa” of the request terminal 10 aa that has sent the login request information as a search key to obtain the terminal ID of another request terminal 10 that has registered the request terminal 10 aa as a candidate terminal. More specifically, referring to FIG. 14, the request terminal 10 aa is listed as a candidate terminal for the request terminal 10 ab, 10 ba, and 10 db. Accordingly, the terminal extractor 54 extracts the terminal IDs “01ab”, “01ba”, and “01db”.

At S30, the terminal state obtainer 55 of the management system 50 searches the terminal state management table stored in the terminal state management DB 5003 (FIG. 13) using the terminal ID “01aa” of the request terminal 10 aa that has sent the login request information as a search key to obtain the operation state of the request terminal 10 aa.

At S31-1 and S31-2, the data transmit/receive 51 of the management system 50 sends the terminal state information including the terminal ID “01aa” and the operation state of the request terminal 10 aa, that are respectively obtained at S30, to the terminals 10 ab, 10 ba, and 10 db each having the request terminal 10 aa as a candidate terminal that is obtained at S29. In this example, the management system 50 sends the terminal state information of the request terminal 10 aa to only the terminals 10 ba and 10 db each having the on-line state as shown in FIG. 13.

More specifically, in this example, the data transmit/receive 51 refers to the terminal management table of FIG. 13 to obtain the IP address of each of the terminals 10 ba and 10 db. Using the obtained IP addresses, the management system 50 is able to send the terminal state information of the request terminal 10 aa to the terminals 10 ba and 10 db each of which lists the request terminal 10 aa as a candidate terminal.

The above-described operation of S21 to S31 is performed by any desired terminal 10 as the power of the terminal 10 is turned on through the power switch 109 (FIG. 5) at S20.

Referring now to FIG. 21, operation of limiting a number of candidate relay terminals 30 is explained according to an example embodiment of the present invention. The operation of FIG. 21 is performed during a management data session sei (FIG. 2), which transmits or receives various management data in the transmission system 1. Further, in this example, the request terminal 10 aa can start communication with at least one of the terminals 10 ba and 10 db each having the on-line state as indicated by the terminal state information received at S28 of FIG. 20. For the descriptive purposes, it is assumed that the user at the request terminal 10 aa starts communication with the counterpart terminal 10 db.

At S41, the user at the request terminal 10 aa operates the operation button 108 to select the terminal 10 db as a counterpart terminal. Upon selection, the operation input 12 (FIG. 7) of the request terminal 10 aa receives a user instruction for starting communication with the counterpart terminal 10 db.

At S42, the data transmit/receive 11 of the request terminal 10 aa sends the communication start request information that requests the management system 50 to start communication with the counterpart terminal 10 db to the management system 50. The communication start request information at least includes identification information such as the terminal ID “01aa” of the request terminal 10 aa and the terminal ID “01db” of the counterpart terminal 10 db.

At the time of receiving the communication start request information, the data transmit/receive 51 of the management system 50 obtains the IP address “1.2.1.3” of the request terminal 10 aa.

At S43, the state manager 53 looks for records in the terminal management DB 5003 (FIG. 13) based on the terminal ID “01aa” of the request terminal 10 aa and the terminal ID “01db” of the counterpart terminal 10 db, which are included in the communication start request information. The state manager 53 changes each of the operation states of the request terminal 10 aa and the counterpart terminal 10 db in the records, from the online state to the communicating state.

At this time, the request terminal 10 aa and the counterpart terminal 10 db has not started communication, but the request terminal 10 aa and the counterpart terminal 10 db each have the communicating state. In case another terminal 10 tries to communicate with the request terminal 10 aa or the counterpart terminal 10 db, the management system 50 causes the another terminal 10 to output voice or display indicating that the request terminal 10 aa or the counterpart terminal 10 db is in the communicating state.

At S44, the management system 50 prepares for a session that is performed for selecting the relay terminal 30 for communication between the request terminal 10 aa and the counterpart terminal 10 db. More specifically, at S44, the session ID generator 56 a (FIG. 9) of the management system 50 generates a session ID for a session that is to be performed for selection of the relay terminal 30.

At S45, the session manager 57 stores the session ID “sel” generated at S44, the terminal ID “01aa” of the request terminal 10 aa, and the terminal ID “01db” of the counterpart terminal 10 db, in the session management DB 5005 (FIG. 15) stored in the memory 5000.

At S46, the primary relay terminal selection unit 56 of the management system 50 limits a number of candidate relay terminals 30 from which one relay terminal 30 to be used for communication between the request terminal 10 aa and the counterpart terminal 10 db is selected, using the relay terminal management DB 5001, the terminal management DB 5003, and the priority management DB 5006.

Referring now to FIG. 9 and FIG. 22, operation performed at S46 of FIG. 21 is explained in detail.

At S46-1 of FIG. 22, the terminal IP address extractor 56 b of the management system 50 searches the terminal management DB 5003 (FIG. 13) using the terminal ID “01aa” of the request terminal 10 aa and the terminal ID “01db” of the counterpart terminal 10 db included in the communication start request information sent from the request terminal 10 aa as a key to obtain the IP addresses of the terminals 10 aa and 10 db, i.e., the IP address “1.2.1.3” and the IP address “1.3.2.4”.

At S46-2, the primary selector 56 c refers to the relay terminal management DB 5001 (FIG. 11) to select one or more relay terminals 30 having the on-line operation state, and obtains the relay terminal ID of the selected relay terminal 30. More specifically, in this example, the primary selector 56 c obtains the relay terminal IDs 111 a, 111 b, and 111 d of the relay terminals 30 a, 30 b, and 30 d.

At S46-3, the primary selector 56 c searches the relay terminal management DB 5001 (FIG. 11) to obtain the IP address of each of the relay terminals 30 a, 30 b, and 30 d, using the relay terminal IDs 111 a, 111 b, and 111 d obtained at S46-2. Further, the primary selector 56 c compares each one of the IP addresses “1.2.1.2”, “1.2.2.2”, and “1.3.2.2” of the relay terminals 30 a, 30 b, and 30 d, with each one of the IP addresses “1.2.1.3” and “1.3.2.4” obtained at S46-1, dot address by dot address, to determine the degree of similarity between the relay terminal IP address and the terminal IP address.

At S46-4, the priority determiner 56 d refers to the priority management DB 5006 (FIG. 16) to determine a value of address priority point for each one of the relay terminals 30 a, 30 b, and 30 d. In this example, as illustrated in FIG. 23, for each one of the relay terminals 30 a, 30 b, and 30 d, the priority determiner 56 d obtains an address priority point with respect to the request terminal 10 aa and an address priority point with respect to the counterpart terminal 10 db.

FIG. 23 illustrates a table storing a calculation result of a priority point, which is used for limiting a number of candidate relay terminals 30. The table of FIG. 23 stores an address priority point, a transmission speed priority point, and a total priority point, for each one of the relay terminals IDs of the relay terminals 30. The address priority point includes a first address priority point with respect to the request terminal 10 aa, and a second address priority point with respect to the counterpart terminal 10 db. The total priority point is obtained by adding the highest one of the first and second address priority points with the transmission speed priority point.

In this example, based on comparison between the IP address “1.2.1.2” of the relay terminal 30 a and the IP address “1.2.1.3” of the request terminal 10 aa, the degree of similarity is “S.S.S.D” such that the address priority point of 5 is obtained. Similarly, based on comparison between the IP address “1.2.1.2” of the relay terminal 30 a and the IP address “1.3.2.4” of the counterpart terminal 10 db, the degree of similarity is “S.D.D.D” such that the address priority point of 1 is obtained.

Based on comparison between the IP address “1.2.2.2” of the relay terminal 30 b and the IP address “1.2.1.3” of the request terminal 10 aa, the degree of similarity is “S.S.D.D” such that the address priority point of 3 is obtained. Similarly, based on comparison between the IP address “1.2.2.2” of the relay terminal 30 b and the IP address “1.3.2.4” of the counterpart terminal 10 db, the degree of similarity is “S.D.S.D” such that the address priority point of 1 is obtained.

Based on comparison between the IP address “1.3.2.2” of the relay terminal 30 d and the IP address “1.2.1.3” of the request terminal 10 aa, the degree of similarity is “S.D.D.D” such that the address priority point of 1 is obtained. Similarly, based on comparison between the IP address “1.3.2.2” of the relay terminal 30 a and the IP address “1.3.2.4” of the counterpart terminal 10 db, the degree of similarity is “S.S.S.D” such that the address priority point of 5 is obtained.

Referring back to FIG. 22, at S46-5, the priority determiner 56 d searches the priority management DB 5006 (FIG. 17) using the maximum data transmission speed of the relay terminal 30 that is stored in the relay terminal management DB 5001 (FIG. 11) to determine a transmission priority point for each one of the relay terminals 30 a, 30 b, and 30 d that are selected at S46-2.

In this example, referring to FIG. 11 and FIG. 17, the relay terminal 30 a having the maximum data transmission speed of 100 Mbps is assigned with the transmission priority point of 3. Similarly, the relay terminal 30 b having the maximum data transmission speed of 1000 Mbps is assigned with the transmission priority point of 5. Similarly, the relay terminal 30 d having the maximum data transmission speed of 10 Mbps is assigned with the transmission priority point of 1. Accordingly, the priority determiner 56 d stores the transmission priority point for each one of the relay terminals 30 a, 30 b, and 30 d in the table of FIG. 23.

At S46-6, for each one of the relay terminals 30 a, 30 b, and 30 d, the primary selector 56 c adds the highest one of the first and second address priority points with the transmission speed priority point to obtain a total priority point. The primary selector 56 c selects the total of two relay terminals 30 having the highest priority point. For example, the primary selector 56 c selects the relay terminal 30 having the highest total priority point and the relay terminal 30 having the second highest total priority point as a candidate relay terminal 30 for further processing. In this example, referring to FIG. 23, the relay terminals 30 a, 30 b, and 30 d having the relay terminal IDs 111 a, 111 b, and 111 d respectively have the total priority points of 8, 8, and 6. Accordingly, the primary selector 56 c selects the relay terminal 30 a having the relay terminal ID 111 a, and the relay terminal 30 b having the relay terminal ID 111 b.

After the operation of S46 illustrated in FIG. 21 completes, at S47 of FIG. 21, the data transmit/receive 51 (FIG. 7) of the management system 50 sends the relay terminal selection information to the counterpart terminal 10 db through the communication network 2. The relay terminal selection information includes a number of candidate relay terminals 30, which is “2”, the terminal ID “01aa” of the request terminal 10 aa, and the session ID “sel” for relay terminal selection. With this relay terminal selection information, the counterpart terminal 10 db is able to obtain information including the number of candidate relay terminals 30, the request terminal 10 aa that requests for videoconference, and the session ID “sel” of the session for relay terminal selection. In addition, the counterpart terminal 10 db obtains the IP address “1.1.1.2” of the management system 50 that has sent the relay terminal selection information.

At S48, the data transmit/receive 11 of the counterpart terminal 10 db sends confirmation information indicating that the relay terminal selection information is received, to the management system 50 through the communication network 2, with the IP address of the counterpart terminal 10 db. The confirmation information includes the session ID “sel”. With this confirmation information, the management system 50 is able to know that the counterpart terminal 10 db is notified with the number of candidate relay terminals 30 obtained during the session sel, and the IP address “1.3.2.4” of the counterpart terminal 10 db.

Referring now to FIGS. 24A, 24B, and 25, operation of selecting the relay terminal 30, performed by the counterpart terminal 10 db, is explained according to an example embodiment of the present invention. The operation of FIGS. 24A and 24B is performed during the management data session sei of FIG. 2, which transmits or receives various management data in the transmission system 1.

Before starting videoconference, at S61-1 and S61-2, the management system 50 sends preparatory relay request information, respectively, to the relay terminals 30 a and 30 b, which are selected by the management system 50 at S46 as candidate relay terminals. The preparatory relay request information requests the relay terminal 30 to perform relay processing before starting the videoconference. More specifically, the preparatory relay request information includes the session ID “sel”, the IP address “1.2.1.3” of the request terminal 10 aa, and the IP address “1.3.2.4” of the counterpart terminal 10 db, and is transmitted with the IP address of the management system 50. With this preparatory relay request information, the relay terminals 30 a and 30 b are each able to obtain information including the session, the request terminal, the counterpart terminal, and the IP address “1.1.1.2” of the management system 50 that has sent the preparatory relay request information.

At S62-1 and S62-2, the relay terminals 30 a and 30 b each cause the data transmit/receive 31 to send preparatory transmit request information to the request terminal 10 aa through the communication network 2. The preparatory transmit request information requests the request terminal 10 aa to send preparatory transmit information including the Packet Internet Grouper (PING) to each one of the relay terminals 30 a and 30 b before starting the videoconference. More specifically, the preparatory transmit request information includes the session ID “sel”, and is transmitted with the IP addresses of the relay terminals 30 a and 30 b. With this preparatory transmit request information, the request terminal 10 aa is able to know that the preparatory transmit information is to be sent during the session with the session ID “sel”, as well as the IP addresses “1.2.1.2” and “1.2.2.2” of the relay terminals 30 a and 30 b.

As described above, the management system 50 does not directly send the IP address of the counterpart terminal 10 db to the request terminal 10 aa. Instead, as described above referring to S61-1 and S61-2, the management system 50 sends the IP address of the counterpart terminal 10 db respectively to the relay terminal 30 a and the relay terminal 30 b. As described above referring to S62-1, the relay terminal 30 aa requests the request terminal 10 aa to send the preparatory transmit information to the relay terminal 30 aa. In this manner, the management system 50 prevents the terminal 10 from obtaining the IP address of another terminal 10, thus improving the security.

At S63-1 and S63-2, the request terminal 10 aa causes the data transmit/receive 11 to send the preparatory transmit information, respectively, to the relay terminals 30 a and 30 b through the communication network 2. The preparatory transmit information is sent to the counterpart terminal 10 db through each one of the relay terminals 30 a and 30 b before the contents data such as the image data and the voice data is transmitted. By sending the preparatory transmit information in replace of the contents data, the management system 50 is able to calculate a time period required for transmitting the contents data from the request terminal 10 aa to the counterpart terminal 10 db through each one of the relay terminals 30 a and 30 b. Further, the preparatory transmit information includes PING information used for checking whether the request terminal 10 aa, the relay terminal 30 a or 30 b, and the counterpart terminal 10 db are each connected to allow communication, the date and time of which the request terminal 10 aa sends the preparatory transmit information, and the session ID “sel”. With this preparatory transmit information, each of the relay terminals 30 a and 30 b knows that the preparatory transmit information is transmitted in the session with the session ID “sel”, and the IP address “1.2.1.3” of the request terminal 10 aa that has sent the preparatory transmit information.

At S64-1 and S64-2, the relay terminals 30 a and 30 b each transmit the preparatory transmit information to the counterpart terminal 10 db having the IP address “1.3.2.4”, which is obtained from the preparatory transmit information. With the preparatory transmit information, the counterpart terminal 10 db is able to know that the preparatory transmit information is transmitted during the session with the session ID “sel”, and the IP addresses “1.2.1.2” and “1.2.2.2” of the relay terminals 30 a and 30 b that respectively send the preparatory transmit information.

At S65, the secondary relay terminal selection unit 17 of the counterpart terminal 10 db selects one of the relay terminals 30 a and 30 b to be used for videoconference, based on the preparatory transmit information.

Referring now to FIG. 8 and FIG. 25, operation of selecting the relay terminal 30 for videoconference, which is performed at S65 of FIG. 24B, is explained.

At S65-1, the counter 16 a of the secondary relay terminal selection unit 16 (FIG. 8) obtains the date and time at which the data transmit/receive 11 of the counterpart terminal 10 db receives the preparatory transmit information for each one of the relay terminals 30 a and 30 b.

At S65-2, the calculator 16 b calculates, for each one of the relay terminals 30 a and 30 b, a time period between the time when the preparatory transmit information is transmitted by the request terminal 10 aa and the time when the preparatory transmit information is received by the counterpart terminal 10 db. The date and time at which the preparatory information is transmitted by the request terminal 10 aa is obtainable from the preparatory transmit information. The date and time of which the preparatory transmit information is received at the counterpart terminal 10 db is obtained by the counter 16 a.

At S65-3, the secondary selector 16 c determines whether all items of preparatory transmit information is received for all of candidate relay terminals, during the session with the session ID “sel”. In this example, the secondary selector 16 c counts a total number of items of preparatory transmit information that have been received, and compares with the total number of candidate relay terminals 30 of “2”.

When it is determined that the preparatory transmit information has not been received for at least one relay terminal 30 (“NO” at S65-3), the operation proceeds to S65-4. When it is determined that the preparatory transmit information has been received for all of the candidate relay terminals 30 (“YES” at S65-3), the operation proceeds to S65-5.

At S65-4, the secondary selector 16 c determines whether a predetermined time period passes after the preparatory transmit information is received at the counterpart terminal 10 db. In this example, the predetermined time period is set to one minute. When it is determined that the predetermined time period has not passed (“NO” at S65-4), the operation returns to S65-1. When it is determined that the predetermined time period has passed (“YES” at S65-4), the operation proceeds to S65-5.

At S65-5, the secondary selector 16 c selects one of the relay terminals 30, which has the least value of the time period required for transmitting the preparatory transmit information based on the calculation of the calculator 16 b.

In this example, it is assumed that the relay terminal 30 a is selected as a time period for transmitting the preparatory transmit information that is relayed through the relay terminal 30 a has a value less than the value of the time period for transmitting the preparatory transmit information that is relayed through the relay terminal 30 b.

Referring back to FIG. 24B, at S66, the data transmit/receive 11 of the counterpart terminal 10 db sends the relay terminal selection information to the management system 50 through the communication network 2. In this example, the relay terminal selection information indicates that the relay terminal 30 a is selected. More specifically, the relay terminal selection information includes the session ID “sel”, and the relay terminal ID “111a” of the selected relay terminal 30 a, and is transmitted with the terminal IP address of the counterpart terminal 10 db. With the relay terminal selection information, the management system 50 is able to know that the relay terminal 30 a has been selected during the session with the session ID “sel”, and the IP address “1.3.2.4” of the counterpart terminal 10 db that has sent the relay terminal selection information.

At S67, the session manager 57 of the management system 50 stores, in the session management table of FIG. 15 stored in the session management DB 5005, the relay terminal ID “111a” of the relay terminal 30 a, which is finally selected for communication, in the “relay terminal ID” field of a record provided for the session with the session ID “sel”.

At S68, the data transmit/receive 51 of the management system 50 sends the relay start request information to the relay terminal 30 a through the communication network 2. The relay start request information requests the relay terminal 30 a to start relay operation. More specifically, the relay start request information includes the IP address “1.2.1.3” of the request terminal 10 aa, and the IP address “1.3.2.4” of the counterpart terminal 10 db.

At S69, the relay terminal 30 a establishes four sessions between the request terminal 10 aa and the counterpart terminal 10 db including a session for transmission of low-level resolution image data, a session for transmission of medium-level resolution image data, a session for transmission of high-level resolution image data, and a session for transmission of voice data. Once these sessions are established, the request terminal 10 aa is able to start videoconference with the counterpart terminal 10 db.

In the above-described example, the management system 50 sends the relay terminal selection information to the counterpart terminal 10 db at S47 (FIG. 21), and the counterpart terminal 10 db performs operation of S48, S64-1 (FIG. 24A), S64-2 (FIG. 24B), and S65 (FIG. 24B) to select the relay terminal 30. In alternative to this example, the management system 50 may send the relay terminal selection information to the request terminal 10 aa to cause the request terminal 10 aa to perform selection of the relay terminal 30. In such case, the request terminal 10 aa performs operation of S48, S64-1 (FIG. 24A), S64-2 (FIG. 24B), and S65 (FIG. 24B) in a substantially similar manner as described above. Further, at S66, the request terminal 10 aa sends the relay terminal selection information to the management system 50.

Referring now to FIG. 7 and FIG. 26, operation of transmitting and receiving contents data such as image data and voice data between the request terminal and the counterpart terminal to carry out videoconference, performed by the transmission system 1, is explained according to an example embodiment of the present invention.

In this example, the contents data such as the image data and the voice data flows in a direction from the request terminal 10 aa to the counterpart terminal 10 db, or in another direction from the counterpart terminal 10 db to the request terminal 10 aa. Since operation such as transmission and reception of the contents data or detection of delay time is the same for both of the directions, the following example focuses on communication in which data flows from the request terminal 10 aa to the counterpart terminal 10 db.

Referring to FIG. 26, at S81, the data transmit/receive 11 of the request terminal 10 aa sends the contents data to the relay terminal 30 a through the communication network 2 in the contents data session “sed”. The contents data includes image data such as image data of an object captured by the imaging unit 14 a and voice data that is input through the voice input 15 a. In this example, it is assumed that the high-quality image data based on the low-level resolution image data, the medium-level resolution image data, and the high-level resolution image data, and the voice data, are transmitted. Accordingly, the data transmit/receive 31 of the relay terminal 30 a receives the image data of three different resolution levels, and the voice data.

At S82, the data quality checker 33 searches the data quality management DB 3001 (FIG. 11) using the IP address “1.3.2.4” of the counterpart terminal 10 db as a key to obtain the quality of the image data to be transmitted to the relay terminal 30 a.

In this example, the quality of image data to be transmitted to the relay terminal 30 a is the high-quality image data. Since the image data that is received at the data transmit/receive 31 has the quality that is the same as the quality of the image data obtained from the data quality management DB 3001, at S83, the relay terminal 30 a sends the high-quality image data and the voice data to the counterpart terminal 10 db in the contents data session “sed”, without applying further image processing.

The counterpart terminal 10 db receives the high quality image data that is generated based on the low-level resolution image data, medium-level resolution image data, and high-level resolution image data, and the voice data, at the data transmit/receive 11. The display control 17 combines the image data of three different resolution levels into the high quality image data for display onto the display 120. Further, the voice output 15 b outputs the voice sound based on the voice data.

At S84, the delay detector 18 of the counterpart terminal 10 db periodically detects a delay time indicating the time at which the image data is received at the data transmit/receive 11, for example, every one second. In this example, it is assumed that the delay time of 200 ms is obtained.

At S85, the data transmit/receive 11 of the counterpart terminal 10 db sends the delay time information indicating the delay time of 200 ms to the management system 50 through the communication network 2, during the management data session “sei”. With the delay time information, the management system 50 is notified of the delay time, and the IP address “1.3.2.4” of the counterpart terminal 10 db that has sent the delay time information.

At S86, the delay time manager 60 of the management system 50 searches the terminal management DB 5003 (FIG. 13) using the IP address “1.3.2.4” of the counterpart terminal 10 db as a search key to extract the terminal ID “01db” of the counterpart terminal 10 db. The delay time manager 60 stores the delay time of 200 ms obtained from the delay time information in a “delay time” field of the record of the terminal ID “01db” of the session management table stored in the session management DB 5005 (FIG. 15).

At S87, the quality determiner 58 searches the quality management DB 5007 (FIG. 18) using the delay time of 200 ms to extract the image data quality of “MEDIUM”. Based on the extracted image data quality, the quality determiner 58 determines that the quality of image data suitable for the delay time of 200 ms is medium.

At S88, the data transmit/receive 51 searches the relay terminal management DB 5001 (FIG. 11) using the relay terminal ID “111a”, which is stored in the session management DB (FIG. 15) in association with the counterpart terminal ID “01db”, to extract the IP address “1.2.1.2” of the relay terminal 30 a.

At S89, the data transmit/receive 51 sends the quality information indicating that the image data quality that has been determined at S87 is medium-level, to the relay terminal 30 a through the communication network 2 during the management data session “sei”. The image quality information is transmitted with the IP address “1.3.2.4” of the counterpart terminal 10 db, which was used as a search key at S86.

At S90, the change quality manager 34 of the relay terminal 30 a stores the IP address “1.3.2.4” of the counterpart terminal 10 db in association with the “medium-level” quality image data to be relayed by the counterpart terminal 10 db, in the data quality management DB 3001 (FIG. 10).

At S91, the request terminal 10 aa transmits the high quality image data including the low-level resolution image data, the medium-level resolution image data, and the high-level resolution image data, and the voice data, to the relay terminal 30 a during the contents data session “sed”, in a substantially similar manner as described above referring to S81.

At S92, the data quality checker 33 of the relay terminal 30 a searches the data quality management DB 3001 (FIG. 10) using the IP address “1.3.2.4” of the counterpart terminal 10 db as a search key to extract the quality of the image data suitable for the counterpart terminal 10 db, in a substantially similar manner as described above referring to S82.

At S93, since the image data quality that is stored for the counterpart terminal 10 db is the medium-level, which is lower than the quality of the image data that is received at the data transmit/receive 31, the data quality changer 35 changes the quality of the image data from the high-level to the medium level. In this example, the quality of the voice data remains the same.

At S94, the data transmit/receive 31 of the relay terminal 30 sends the image data having the quality that is lowered to the medium-level, and the voice data, to the counterpart terminal 10 db through the communication network 2, during the contents data session “sed”. The data transmit/receive 11 of the counterpart terminal 10 db receives the medium-quality image data that is generated based on the low-level resolution image data and the medium-level resolution image data, and the voice data. The display control 17 of the counterpart terminal 10 db combines the image data of two different resolution levels to generate the medium-level image data for display on the display 120. Further, the voice output 15 db outputs the voice sound generated based on the voice data.

As described above, when any delay in receiving the image data at the counterpart terminal 10 db is observed, the relay terminal 30 a changes the quality of image data by lowering the quality of image data. Accordingly, the users participating the videoconference are able to carry out communication more smoothly.

Referring now to FIG. 33, operation of transmitting event data, performed by the transmission system 1 of FIG. 1, is explained according to an example embodiment of the present invention. In this example, it is assumed that the request terminal 10 aa communicates with the counterpart terminals 10 db to carry out videoconference.

At S51, an event occurs at the request terminal 10 aa. For example, it is assumed that the even identification data of the event includes the event main class of “OPERATION”, the event sub-class of “PICTURE”, and the event name of “START”. When the event occurs, at S52, the request terminal 10 aa sends the event data to the management system 50 through the data transmit/receive 11. The management system 50 receives the event data at the data transmit/event 51. In this example, the event data includes the event identification data of the event such as the event main class of “OPERATION”, the event sub-class of “PICTURE”, and the event name of “START”, and the terminal ID “01aa” of the request terminal 10 that created the event.

Referring now to FIG. 34, operation of transmitting event data based on the event data received from the request terminal 10, performed by the management system 50, is explained according to an example embodiment of the present invention. The operation of transmitting event data of FIG. 34 is performed at S53 of FIG. 3.

At S53-1, the data transmit/receive 51 of the management system 50 receives the event data from the request terminal 10 aa.

At S53-2, the importance level obtainer 61 a of the event data transmit 61 searches the event management table of FIG. 28 stored in the event data management DB 5009 using the event identification data of the event data as a search key to obtain the importance level of the event data. In this example, the event identification data of the event data includes the event main class of “OPERATION”, the event sub-class of “PICTURE”, and the event name of “START”. Accordingly, the importance level of “HIGH” is obtained for the received event data.

At S53-3, the first property data obtainer 61 b 1 of the property data obtainer 61 b searches the property data management DB 5008 using the terminal ID “01aa” extracted from the event data to obtain the property data of the request terminal 10 aa. Referring to FIG. 27, the company name of “COMPANY A” and the country name of “JAPAN” are obtained for the request terminal 10 aa.

At S53-4, the communicating terminal data obtainer 61 b 2 searches the session management table of FIG. 15 stored in the session management DB 5005 using the terminal ID “01aa” of the request terminal 10 as a search key to obtain the terminal ID of the counterpart terminal 10 as the terminal ID of the communicating terminal 10. In this example, the terminal ID “01db” of the counterpart terminal 10 db is obtained.

At S53-5, the second property data obtainer 61 b 3 searches the property data management table of FIG. 27 stored in the property data management DB 5008 using the terminal ID “01db” of the counterpart terminal 10 db as a search key to obtain the property data of the counterpart terminal 10 db. In this example, the company name “COMPANY A” and the country name “USA” is obtained for the counterpart terminal 10 db.

At S53-6, the determiner 61 c determines whether the property data of the request terminal 10 aa having the terminal ID “01aa” that is obtained by the first property data obtainer 61 b 1 is the same as the property data of the counterpart terminal 10 db having the terminal ID “01db” that is obtained by the second property data obtainer 61 b 3 to obtain similarity in property data between the request terminal 10 aa and the counterpart terminal 10 db. More specifically, the company name “COMPANY A” of the request terminal 10 aa is compared with the company name “COMPANY A” of the counterpart terminal 10 db to obtain a determination result indicating that the company name is the same. The country name “JAPAN” of the request terminal 10 aa is compared with the country name “USA” of the counterpart terminal 10 db to obtain a determination result indicating that the country name is different.

At S53-7, the destination extractor 61 b searches the destination management table of FIG. 29 stored in the destination management DB 5010 using a combination of the determination result indicating that the company name is the same and that the country name is different, and the importance level of “HIGH”, to obtain one or more destinations to which the event data is to be transmitted. In this example, the destination is any terminal 10 having the same company name as the company name of the request terminal 10 aa that created the event. The destination extractor 61 d further extracts one or more terminals 10 having the same company name “COMPANY A” using the property data management table of FIG. 27 stored in the property data management DB 5008. More specifically, in this example, the destination extractor 61 d searches the property data management table of FIG. 27 stored in the property data management DB 5008 using the company name “COMPANY A” of the request terminal 10 aa to obtain the terminal ID “01ab” and the terminal ID “Okla”. In this example, the terminal ID “01db” of the terminal 10 db is not extracted as the terminal 10 db is the communicating terminal 10.

At S54-1 to S54-2, the data transmit/receive 51 of the management system 50 transmits the event data to the terminals 10 having the terminal IDs that are extracted by the destination extractor 61 d. In this example, the data transmit/receive 51 transmits the event data to the terminal 10 ab having the terminal ID “01ab” and the terminal 10 da having the terminal ID “01da”, respectively.

More specifically, in this example, the data transmit/receive 51 may obtain the IP address for each one of the terminal 10 ab and the terminal 10 da, for example, by referring to the terminal management DB 5003 (FIG. 13), and respectively send the event data to the terminal 10 ab and the terminal 10 da using the obtained IP addresses. In alternative to the IP address, any identification information may be used to specify the terminal 10 such as the URI or email address.

At S54-3, when the destination to which the event data is to be transmitted includes the event log management system 80, the management system 50 transmits the event data to the event log management system 80.

Further, in this example, the management system 50 is assumed to transmit the event data to the communicating terminal 10 db having videoconference with the request terminal 10 aa.

The operation of FIG. 33 may be performed in various other ways. For example, at S53-7, after the destination extractor 61 b extracts the terminal ID of the destination terminal 10 to which notification is to be transmitted, the destination extractor 61 b may further search the candidate list management table of FIG. 14 to determine whether the extracted terminal ID of the destination terminal is stored in association with the request terminal 10 as a candidate counterpart terminal ID of a candidate counterpart terminal 10. When it is determined that the extracted terminal ID of the destination terminal is stored in association with the request terminal 10, the destination extractor 61 b causes the data transmit/receive 51 to send notification to the destination terminal 10. When it is determined that the extracted terminal ID of the destination terminal is not stored in association with the request terminal 10, the destination extractor 61 b determines not to transmit notification to the destination terminal having the extracted terminal ID. In this manner, a number of destination terminals to which notification is to be transmitted may be further reduced.

Alternatively, at S53-7, after the destination extractor 61 b extracts the terminal ID of the destination terminal 10 to which notification is to be transmitted, the destination extractor 61 b may further search the candidate list management table of FIG. 14 to determine whether the extracted terminal ID of the destination terminal is stored in association with the request terminal 10 as a counterpart terminal ID of a counterpart terminal 10 that lists the request terminal 10 as a candidate counterpart terminal. When it is determined that the extracted terminal ID of the destination terminal is stored in association with the request terminal 10, the destination extractor 61 b causes the data transmit/receive 51 to send notification to the destination terminal 10. When it is determined that the extracted terminal ID of the destination terminal is not stored in association with the request terminal 10, the destination extractor 61 b determines not to transmit notification to the destination terminal having the extracted terminal ID. In this manner, a number of destination terminals to which notification is to be transmitted may be further reduced.

In another example, in alternative to managing the event identification data using the terminal 10 that created the event, the event identification data may be managed in terms of the session ID for uniquely identifying a session established between the request terminal 10A and the counterpart terminal 10B. In such case, the event data may include the event identification data indicating the operation or the state of the event, and the session ID for identifying the session in which the event occurred.

In another example, any one of the above-described functions performed by the management system 50 may be performed by the terminal 10. In another example, the function or operation of the event log management system 80 may be performed by the management system 50.

At the event log management system 80, the data transmit/receive 81 receives the event data from the management system 50. The memory control 89 stores the event data in the event log management DB 8001. For example, referring to FIG. 32, the memory control 89 stores the event ID of the event, the date and time at which the event occurred, and the event data including the event main class, the event sub-class, the event name, and the terminal ID of the terminal 10 creating the event.

As described above, the transmission system 1 transmits notification such as event data based on similarity in property data between the terminal 10 that created the event and the counterpart terminal 10 that is communicating with the terminal 10. For example, the transmission management system 50 determines a destination to which the event data is to be transmitted, based on the similarity in company name between the terminals 10 and the similarity in country name between the terminals 10. In this manner, the transmission management system 50 transmits event data to the terminal 10 when the event data to be transmitted is most likely to be related to the terminal 10, and the transmission management system 50 does not transmit event data to the terminal 10 when the event data to be transmitted is not most likely to be related to the terminal 10. This suppresses the workload of the transmission management system 50 as the management system 50 is able to reduce a number of destinations to be transmitted when the event occurred. Further, since the terminal 10 is notified of event data that is most likely to be related to the terminal 10, the terminal 10 does not have to look for the event data that is important to the terminal 10.

Further, as described above, the transmission system is provided with a function of selecting one of a plurality of relay terminals 30 that is suitable for communication between a request terminal and a counterpart terminal. While it may be difficult to obtain information regarding the entire network such as the Internet, the transmission system 1 is able to identify the relay terminal that is suitable for communication using information available from the communication network such as information regarding the LAN at which the relay terminal is located.

More specifically, the management system 50 selects a small number of relay terminals 30 out of a large number of relay terminals 30 for further processing. Preferably, the small number of relay terminals 30 is equal to or more than two. Before sending contents data from the request terminal 10 to the counterpart terminal 10, the management system 50 causes the request terminal 10 to send preparatory transmit information to the counterpart terminal 10 via each one of the selected relay terminals 30 to obtain information regarding a time required for transmitting the preparatory transmit information for each one of the selected relay terminals 30. Based on this obtained information, the relay terminal 30 that is most suitable for communication between the request terminal and the counterpart terminal is selected.

In one example, the management system 50 selects a small number of relay terminals 30 each having the IP address that is similar to at least one of the IP address of the request terminal and the IP address of the counterpart terminal. Once the relay terminals 30 are selected, the management system 50 causes the request terminal 10 to send preparatory transmit information to the counterpart terminal 10 via each one of the selected relay terminals 30 to obtain a time required for transmitting the preparatory transmit information for each one of the selected relay terminals 30. The relay terminal 30 with a smallest value of the time for transmitting the preparatory transmit information is selected. Since the relay terminal 30 is selected based on information obtained using the actual communication network, the request terminal and the counterpart terminal are able to exchange high-quality image data and voice data with relatively high transmission speeds.

Additionally or alternatively, in order to select a small number of relay terminals 30, the maximum data transmission speed of the relay terminal 30 may be taken into account. Once the relay terminals 30 are selected, the management system 50 causes the request terminal 10A to send preparatory transmit information to the counterpart terminal 10B via each one of the selected relay terminals 30 to obtain a time required for transmitting the preparatory transmit information for each one of the selected relay terminals 30. The relay terminal 30 with a smallest value of the time for transmitting the preparatory transmit information is selected. Since the relay terminal 30 is selected based on information obtained using the actual communication network, the request terminal 10A and the counterpart terminal 10B are able to exchange high-quality image data and voice data with relatively high transmission speeds.

Additionally or alternatively, in order to select a small number of relay terminals 30, whether the relay terminal 30 is in the on-line state or not may be taken into account. Since the relay terminal 30 is selected based on the current operation state of the relay terminal 30, the relay terminal 30 is selected with improved accuracy.

The relay terminal 30, the management system 50, the event log management system 80, the program providing system 90, and the maintenance system 100 may be each implemented by a single computer. Alternatively, any number of parts, functions, or modules of the relay terminal 30, the management system 50, the event log management system 80, the program providing system 90, and the maintenance system 100 may be classified into a desired number of groups to be carried out by a plurality of computers. In case the program providing system 90 is implemented by the single computer, the program to be provided by the program providing system 90 may be transmitted, one module by one module, after dividing into a plurality of modules, or may be transmitted at once. In case the program providing system 90 is implemented as a plurality of computers, each computer may transmit each module that is stored in its memory, after the program is divided into a plurality of modules.

The recording medium storing any one of the terminal control program, relay control program, event log management program, and transmission management program, or a storage device such as the HDD 204 that stores any one of the terminal control program, relay control program, event log management program, and transmission management program, or the program providing system 90 provided with the HD 204 storing any one of the terminal control program, relay control program, event log management program, and transmission management program, may be distributed within the country or to another country as a computer program product.

In the above-described examples, the quality of image data to be processed by the relay terminal 30, which is determined based on information obtainable from any one of the data quality management table of FIG. 10 and the quality management table of FIG. 18 is analyzed in terms of image resolution. Alternatively, any other criteria may be used to analyze quality of image data including, for example, depth of image, sampling frequency in case of voice data, and bit length in case of voice data.

Further, the date and time information stored in the relay terminal management table of FIG. 11 or the terminal management table of FIG. 13, or the delay time information stored in the session management table of FIG. 15, is expressed in terms of date and time. Alternatively, the date and time information or the delay time information may be expressed only in terms of time such as the time at which information is received.

Further, in the above-described examples, the relay terminal IP address of the relay terminal 30 and the terminal IP address of the terminal 10 are respectively managed using the relay terminal management table of FIG. 11 and the terminal management table of FIG. 13. Alternatively, the relay terminal 30 and the terminal 10 may each be managed using any other identification information or using any other tables. For example, when the relay terminal 30 or the terminal 10 needs to be identified on the communication network 2, the relay terminal 30 or the terminal 10 may be managed using Fully Qualified Domain Name (FQDN). In such case, the transmission system 10 is provided with a domain name system (DNS) server that obtains the IP address that corresponds to the FQDN of the relay terminal 30 or the terminal 10. In view of this, identification information for identifying the relay terminal 30 on the communication network 2 may not only include the identification information that identifies the relay terminal 30 on the communication network 2, but also identification information that identifies a node on the communication network 2 to which the relay terminal 30 is connected, or identification information that identifies a node on the communication network 2 from which the relay terminal 30 is connected. Similarly, identification information for identifying the terminal 10 on the communication network 2 may not only include the identification information that identifies the terminal 10 on the communication network 2, but also identification information that identifies a node on the communication network 2 to which the terminal 10 is connected, or identification information that identifies a node on the communication network 2 from which the terminal 10 is connected.

In the above-described examples, the transmission system 1 of FIG. 1 is treated as a videoconference system. Alternatively, the transmission system 1 of FIG. 1 may be implemented as a teleconference system such as the IP teleconference system or the Internet teleconference system. Alternatively, the transmission system 1 of FIG. 1 may be implemented as a car navigation system. For example, the request terminal 10 may be implemented as a car navigation system that is installed onto an automobile. The counterpart terminal 10 may be implemented as a management terminal or server at a management center that manages the car navigation system or a car navigation system that is installed onto another automobile. In another example, the transmission system 1 of FIG. 1 may be implemented as a communication system having a portable phone. In such case, the terminal 10 is implemented as the portable phone.

In the above-described examples, the contents data is assumed to include image data and voice data. Alternatively, the contents data may include any other type of data that affects human senses of sight in alternative to image data, or any other type of data that affects human senses of hearing in alternative to voice data. Alternatively, the contents data may include any other type of data that affects human senses of sight, smell, taste, touch, and hearing. In case the contents data that affects human senses of touch, the terminal 10 may convey the contents data that reflects senses of touch that is felt by a user at the terminal 10 to another terminal 10 through the communication network 2. In case the contents data that affects human senses of smell, the terminal 10 may convey the contents data that affects senses of smell felt by a user at the terminal 10 to another terminal 10 through the communication network 2. In case the contents data that affects human senses of taste, the terminal 10 may convey the contents data that affects senses of taste felt by a user at the terminal 10 to another terminal 10 through the communication network 2.

Further, the contents data may only include one type of contents data selected from sight data such as image data, hearing data such as voice data, touch data, smell data, and taste data.

Further, in the above-described examples, the transmissions system 1 is implemented as a videoconference system for use at offices. Other examples of use of the transmission system 1 include, but not limited to, meetings, casual conversation among family members or friends, and distribution of information in one direction.

Further, in the above-described examples, event data is transmitted based on the importance level of event data and whether property data is the same or different. Alternatively, event data is transmitted based on at least one of the importance level and the property data.

Further, in the above-described examples, one or more destination to which even data is to be transmitted is determined based on the importance level of the event data and the similarity in property data. Alternatively, one or more destination to which event data is to be transmitted may be determined based on only one of the importance level of the event data and the similarity in property data.

Numerous additional modifications and variations are possible in light of the above teachings. It is therefore to be understood that within the scope of the appended claims, the disclosure of the present invention may be practiced otherwise than as specifically described herein.

With some embodiments of the present invention having thus been described, it will be obvious that the same may be varied in many ways. Such variations are not to be regarded as a departure from the spirit and scope of the present invention, and all such modifications are intended to be included within the scope of the present invention.

For example, elements and/or features of different illustrative embodiments may be combined with each other and/or substituted for each other within the scope of this disclosure and appended claims.

Further, as described above, any one of the above-described and other methods of the present invention may be embodied in the form of a computer program stored in any kind of storage medium. Examples of storage mediums include, but are not limited to, flexible disk, hard disk, optical discs, magneto-optical discs, magnetic tapes, involatile memory cards, ROM (read-only-memory), etc.

Alternatively, any one of the above-described and other methods of the present invention may be implemented by ASIC, prepared by interconnecting an appropriate network of conventional component circuits or by a combination thereof with one or more conventional general purpose microprocessors and/or signal processors programmed accordingly.

In one example, the present invention may reside in a transmission management system for managing a transmission terminal that transmits or receives data to or from a counterpart transmission terminal. The transmission management system includes a destination management storage to store a destination to which event data is to be transmitted, in association with similarity information indicating whether property data of the transmission terminal is the same as property data of the counterpart terminal, the event data indicating an operation or a state of the transmission terminal; a property data obtainer to obtain the property data of the transmission terminal and the property data of the counterpart terminal; a determiner to determine the similarity between the property data of the transmission terminal and the property data of the counterpart terminal; a destination extractor to extract a destination to which the event data is to be transmitted from the destination management storage using the similarity obtained by the determiner; and an event data transmit to transmit the event data to the destination extracted by the destination extractor.

In the above-described example, the transmission management system further includes: a property data storage to store identification information for identifying the transmission terminal in association with the property data of the transmission terminal; a first property data obtainer to search the property data storage using the identification information of the transmission terminal to obtain the property data corresponding to the identification information of the transmission terminal; and a second property data obtainer to search the property data storage using identification information of the counterpart terminal to obtain the property data corresponding to the identification information of the counterpart terminal. The determiner determines whether the property data obtained by the first property data obtainer is the same as the property data obtained by the second property data obtainer.

In the above-described example, the transmission management system includes a session management storage to store the identification information of the counterpart terminal in association with the identification information of the transmission terminal. The second property data obtainer includes a communicating identification information obtainer to search the session management storage using the identification information of the transmission terminal to obtain the identification information of the counterpart terminal.

In the above-described example, the transmission management system further includes: a candidate counterpart terminal data storage to store identification information of a candidate transmission terminal in association with the identification information of the transmission terminal. The event data transmit transmits the event data to the destination when the identification information of the destination is stored in association with the identification information of the transmission terminal in the candidate counterpart terminal data storage.

In any one of the above-described examples, the destination storage stores the destination information indicating the destination to which the event data is to be transmitted in association with a combination of the importance level indicating the degree of importance of the event data and information indicating the similarity in property data. The destination extractor includes an importance level obtainer to obtain the importance level of the even data, and searches the destination storage using the combination of the importance level of the event data obtained by the importance level obtainer and the similarity in property data obtained by the determiner, to obtain the destination information.

In any one of the above-described examples, the event data includes event identification data for identifying the operation or the state of the event. The transmission management system further includes an importance level storage to store the event identification data in association with the importance level of the event data. The importance level obtainer searches the importance level storage using the event identification data of the event data to obtain the importance level of the event data.

In another example, the present invention may reside in a method of managing a transmission management system for managing a transmission terminal that transmits or receives data to or from a counterpart transmission terminal. The transmission management method includes: storing, in a memory, a destination to which event data is to be transmitted in association with similarity information indicating whether property data of the transmission terminal is the same as property data of the counterpart terminal, the event data indicating an operation or a state of the transmission terminal; obtaining the property data of the transmission terminal and the property data of the counterpart terminal; determining the similarity between the property data of the transmission terminal and the property data of the counterpart terminal; extracting a destination to which the event data is to be transmitted from the memory using the similarity obtained by the determining; and transmitting the event data to the destination extracted by the extracting.

In another example, the present invention may reside in a recording medium storing a plurality of instructions which, when executed by a processor, cause the processor to perform the above-described transmission management method.

In another example, the present invention may reside in method of managing a plurality of terminals including: receiving event data from a transmission terminal, the event data indicating an event created by the transmission terminal when communicating with a counterpart terminal; obtaining property data of the transmission terminal and property data of the counterpart terminal; determining whether the property data of the transmission terminal matches the property data of the counterpart terminal to generate similarity information indicating the degree of similarity between the property data of the transmission terminal and the property data of the counterpart terminal; extracting a destination to which the event data is to be transmitted using the similarity information obtained by the determining; and transmitting the event data to the destination.

In the above-described example, the method further includes: storing, in a memory, similarity information indicating the degree of similarity between property data of a first terminal and property data of a second terminal in association with destination information that specifies a destination to which event data of the first terminal is to be transmitted; obtaining, from the memory, destination information that is stored in association with the similarity information obtained by the determining; and extracting the destination to which the event data is to be transmitted using the destination information.

In the above-described example, the method further includes: storing, in the memory, for each one of the plurality of terminals, property data in association with identification information of the terminal; extracting identification information of the transmission terminal from the event data; obtaining the property data of the transmission terminal from the memory using the identification information of the transmission terminal; obtaining the property data of the counterpart terminal from the memory using identification information of the counterpart terminal.

In the above-described example, the method further includes: storing, in the memory, for each session that carries out communication between a first terminal and a second terminal, identification information of the first terminal in association with identification information of the second terminal; and obtaining, from the memory, the identification information of the counterpart terminal that is stored in association with the identification information of the transmission terminal.

In the above-described example, the method further includes: storing, in the memory, for each one of the plurality of terminals, identification information of a candidate terminal in association with identification information of a terminal, wherein the transmitting includes: transmitting the event data to the destination when identification information of the destination is stored in the memory in association with the identification information of the transmission terminal.

In the above-described example, the method further includes: obtaining importance level of the event created by the transmission terminal; and extracting the destination to which the event data is to be transmitted using the importance level obtained by the obtaining in addition to the similarity information obtained by the determining.

In the above-described example, the method further includes: storing, in a memory, similarity information indicating the degree of similarity between property data of a first terminal and property data of a second terminal, and importance level information indicating an importance level of an event created by the first terminal, in association with destination information that specifies a destination to which event data of the first terminal is to be transmitted; obtaining, from the memory, destination information that is stored in association with the importance level obtained by the obtaining and the similarity information obtained by the determining: and extracting the destination to which the event data is to be transmitted using the destination information.

In the above-described example, the method further includes: storing, in the memory, for each one of events, an importance level of the event in association with event identification data for identifying the event; and obtaining, from the memory, an importance level of the event created by the transmission terminal using event identification data obtained from the event data received from the transmission terminal.

In the above-described example, the property data of the transmission terminal includes at least one of: information for identifying an organization that owns the transmission terminal; and information for identifying a location where the organization that owns the transmission terminal is located.

In the above-described example, the destination to which the event data is to be transmitted includes at least one of: a transmission terminal that matches a condition defined by the destination information; and an event log management system to store log information in a memory. 

1. (canceled)
 2. A transmission manager to manage a plurality of terminals, comprising: a receiver to receive event data from a transmission terminal, the event data including identification information of the transmission terminal and indicating an event created by the transmission terminal when the transmission terminal is communicating with a counterpart terminal; a memory to store for each of the plurality of terminals, property data in association with the identification information of the terminal; a property data obtainer, implemented using one or more processors, to obtain property data of the transmission terminal and property data of the counterpart terminal that is communicating with the transmission terminal, from the memory using identification information included in the event data that is received from the transmission terminal; a determiner, implemented by the one or more processors, to determine whether the property data of the transmission terminal matches the property data of the counterpart terminal, and to generate a determination result based on a determination of matching; and, a transmitter to transmit the event data to a destination that is determined using the determination result.
 3. The transmission manager of claim 2, further comprising: a destination management memory configured to store the determination result in association with destination information that specifies the destination to which the event data is to be transmitted, wherein the destination to which the event data is to be transmitted is identified using the destination information that is stored in association with the determination result.
 4. The transmission manager of claim 2, wherein the property data obtainer includes: a first property data obtainer implemented by the one or more processors to extract identification information of the transmission terminal from the event data, and to obtain the property data of the transmission terminal from the memory using the identification information of the transmission terminal; and a second property data obtainer implemented by the one or more processors and configured to obtain the property data of the counterpart terminal from the memory using identification information of the counterpart terminal.
 5. The transmission manager of claim 4, further comprising: a session management memory to store, for each session that carries out communication between a first terminal and a second terminal, identification information of the first terminal in association with identification information of the second terminal, wherein the second property data obtainer obtains, from the session management memory, the identification information of the counterpart terminal that is stored in association with the identification information of the transmission terminal.
 6. The transmission manager of claim 5, further comprising: a candidate counterpart terminal memory to store, for each one of the plurality of terminals, identification information of a candidate terminal in association with identification information of a terminal, wherein the transmitter transmits the event data to the destination when the event data transmitter determines that the candidate counterpart terminal storage stores identification information of the destination in association with the identification information of the transmission terminal.
 7. The transmission manager of claim 2, further comprising: an importance level obtainer implemented by the one or more processors and configured to obtain an importance level of the event created by the transmission terminal; and a destination extractor, implemented by the one or more processors, to extract the destination to which the event data is to be transmitted using the importance level obtained by the importance level obtainer in addition to the determination result determined by the determiner.
 8. The transmission manager of claim 7, further comprising: a destination management memory to store similarity information indicating the degree of similarity between property data of the first terminal and property data of a second terminal, and importance level information indicating an importance level of an event created by the first terminal, in association with destination information that specifies a destination to which event data of the first terminal is to be transmitted; and a destination extractor to obtain, from the destination management memory, destination information that is stored in association with the importance level of the event obtained by the importance level obtainer and the determination result obtained by the determiner, and to extract the destination to which the event data is to be transmitted using the destination information.
 9. The transmission manager of claim 8, further comprising: an importance level memory to store, for each event, an importance level of the event in association with event identification data for identifying the event, wherein the importance level obtainer obtains, from the importance level memory, an importance level of the event created by the transmission terminal using event identification data obtained from the event data received from the transmission terminal.
 10. The transmission manager of claim 2, wherein the property data of the transmission terminal includes at least one of information for identifying an organization that owns the transmission terminal and information for identifying a location where the organization that owns the transmission terminal is located.
 11. The transmission manager of claim 2, wherein the destination to which the event data is to be transmitted includes at least one of a transmission terminal that matches a condition defined by the destination information and an event log management system to store log information in a memory.
 12. A method of managing a plurality of terminals, the method comprising: receiving event data from a transmission terminal, the event data including an identification information of the transmission terminal and indicating an event created by the transmission terminal when communicating with a counterpart terminal; storing, in a memory, identification information of the plurality of terminals; obtaining property data of the transmission terminal and property data of the counterpart terminal, the property data of the counterpart terminal being obtained by using identification information of the transmission terminal included in the event data that is received from the transmission terminal; determining whether the property data of the transmission terminal matches the property data of the counterpart terminal, and generating a determination result based on a determination of matching; and transmitting the event data to a destination that is determined using the determination result.
 13. The method of claim 12, further comprising: storing, in a destination management memory, the determination result in association with destination information that specifies the destination to which the event data is to be transmitted, wherein the destination to which the event data is to be transmitted is identified using the destination information that is stored in association with the determination result.
 14. A system comprising: a transmission terminal; and a transmission manager to manage a plurality of terminals, the transmission manager comprising: a receiver to receive event data from the transmission terminal, the event data including identification information of the transmission terminal and indicating an event created by the transmission terminal when the transmission terminal is communicating with a counterpart terminal; a memory to store for each of the plurality of terminals, property data in association with the identification information of the terminal; a property data obtainer, implemented using one or more processors, to obtain property data of the transmission terminal and property data of the counterpart terminal that is communicating with the transmission terminal, from the memory using identification information included in the event data that is received from the transmission terminal; a determiner, implemented by the one or more processors, to determine whether the property data of the transmission terminal matches the property data of the counterpart terminal, and to generate a determination result based on a determination of matching; and, a transmitter to transmit the event data to a destination that is determined using the determination result.
 15. The system of claim 14, wherein the transmission manager further comprises: a destination management memory configured to store the determination result in association with destination information that specifies the destination to which the event data is to be transmitted, wherein the destination to which the event data is to be transmitted is identified using the destination information that is stored in association with the determination result 